Explain why an order needs attention
Approval is more than a yes-or-no status. Reason chips identify credit, stock or pricing issues and route attention to the people who can resolve them.
Distribution & operations
Project overviewDistrova ERP: Follow the order through the operation.
Distrova ERPProduct videos
Distrova ERP connects distributors’ field sales, warehouse teams, drivers and finance in one order-to-cash workflow. A management portal and dedicated mobile apps carry orders through approval, fulfilment, delivery and collections, giving each team a clear view of its next step.
The distribution operations challenge
The order crosses several teams. Credit, stock, approval and fulfilment decisions need to stay connected to the same record.
Who Distrova ERP connects
Sales and shop users
Capture the order context.
Warehouse
Prepare approved work for fulfilment.
Driver and office
Record delivery and commercial follow-through.
What Distrova ERP brings together
Order controls
Review pricing, credit and available stock.
Warehouse handoff
Connect approval, reservation and picking.
Delivery and collections
Keep proof, balances and follow-up tied to the order.
Follow the journey
01
Capture
Record the order and customer context.
02
Review
Apply the relevant approval and stock checks.
03
Fulfil
Pick, prepare and dispatch the order.
04
Close the loop
Record delivery, collection or return activity.
Distribution workflow is the focus. Region-specific accounting, taxation and compliance requirements need their own review.
Order journey
ER-204Item A · Qty 12
PricingChecked
CreditWithin limit
StockAvailable
Explore the workflow
A distribution workflow connecting sales, warehouse work, delivery evidence and collections.
Product engineering story
Keep the order together as the work changes handsInside the build
The decisions behind the experience.
Distrova ERP connects a distribution business across companies, warehouses and field teams. Taking an order is only the start: credit and pricing need checks, stock needs reservation, warehouse staff need pick lists, drivers need delivery information and finance needs to reconcile collections. The product is organised around that complete order-to-cash journey.
The design brief
Make every order handoff deliberate, from the shop to fulfilment and collection.
An order is a sequence of responsibilities. Every handoff needs a clear owner and an accurate record.
The constraint
A shop-submitted order can need salesperson review before the approval gate. Holding stock too early would treat an unreviewed request as a fulfilment commitment.
The tradeoff
The review stage adds a handoff, but preserves ownership: the assigned salesperson can review quantities while pricing controls remain distinct. Forwarding the order then invokes the approval process.
Product scope
5
Connected surfaces
One management portal and four Android apps
15
Defined roles
From company administration to shop customers
6
Core approval checks
Customer status, credit, overdue bills, stock, discount and value/pricing
Give each field role a focused app
Sales, warehouse, driver and shop apps expose different tasks. Pickers scan items; drivers capture delivery evidence and collections; shop users see their own orders and account.
Treat cash handover as a workflow
A field collection and an office-verified remittance are separate events. Recording both makes the handover visible rather than assuming that delivered goods mean settled cash.
A workflow in practice
From the trigger to the handoff.
A representative scenario through the implemented workflow.
- 01 · The situation
A shop submits an order in a zone with an assigned salesperson.
- 02 · The product response
The order waits for salesperson review without reserving stock. Forwarding moves it to the approval gate; rejection records a reason.
- 03 · The next step
Warehouse work begins from the approved flow, with downstream delivery and collection records attached to the order journey.
How it is built
The structure behind the workflow.
Role-specific experiences
React provides the management portal. A shared Flutter package supports four Android apps with consistent sign-in and interface foundations.
ERP services
Django services connect sales, dispatch, inventory, procurement and finance across the selected company.
Data & accountability
Role permissions hide cost and margin from field roles. Audit records and company-scoped reports support operational review.
Actual product screens
The product, up close.
The order card makes the credit and approval context visible before a decision.
Original product interface captures. Screens use demonstration data; visible figures are not measured customer results.
System map
Connected by design.
SYSTEM BLUEPRINT / Distrova ERP
Select a component to exploreConnected by design.
01 The experiences
02 The shared foundation
03 What it connects
THE COMPLETE PICTURE
Company-scoped ERP services
Four Flutter Android apps and a React portal share a Django backend. Company scoping and role permissions control access.
| The work | Problem addressed | With Distrova ERP |
|---|---|---|
| Order exceptions | Calls to discover why an order is held | Visible approval reasons and accountable decisions |
| Warehouse handoff | Paper lists disconnected from the order | Pick and pack workflows linked to approved orders |
| Cash collection | Field totals reconciled informally | Recorded collections and verified office remittances |
| Multiple companies | Separate views without shared context | Company-scoped operations with supported cross-company billing |
Delivered capability
Inside Distrova ERP.
Distrova ERP creates a traceable chain from the shop order through fulfilment and collections. The product’s value is in the handoffs: each role sees the work it owns, while management can follow the order across the whole process.
Operational software needs to model the exception as carefully as the happy path. A blocked order becomes actionable when the reason and the responsible role are clear.
Evidence & evaluation
What this case study establishes.
Order-review service and product architecture brief. The brief retains the former Excellent ERP name; the portfolio uses the current Distrova brand.
This is a product engineering case study based on source code, project documentation and recorded screens. It describes implemented capabilities; customer performance gains have not been measured for this case study.
What to measure next
Suggested measures for a deployment evaluation, not reported results.
- Time spent in salesperson review and approval
- Orders blocked by credit, stock or pricing reason
- Field collections awaiting office reconciliation
Discuss the fit
Company access, data migration, integrations and local operating requirements are assessed before an implementation is scoped.