Supplier delivery management system
A supplier delivery management system: prices customised per customer group, with different customer...
View Details →Challenges
The client sits in the middle of the chain: marketplace shops upstream, dozens of contract factories downstream. The process itself is clear — the breaks are all in moving information by hand.
Orders lived in the ERP, purchasing in spreadsheets, stock in a warehouse manager's memory. Every sync meant re-typing fields: platform order numbers did not match purchase orders, and month-end reconciliation felt like archaeology.
Suppliers took orders from group chats, chased progress by phone, and reconstructed piece-rate pay at month end. Who was on which step, how many reworks, how much to pay — all of it rested on trust. Trust is not a ledger.
Marketplace return data sat in the seller back office; suppliers never learned how much of their output came back or why. Without returns flowing to the factory, quality management had no lever.
One judgement shaped the whole platform: the hard part of cross-border fulfilment is not taking the order — it is translating one overseas order into three languages a factory can execute, a warehouse can ship, and finance can reconcile. So ERP integration and the order spine came first; collaboration and scoring came second.
Modules
The web back end serves operations and warehouse staff; the supplier end serves contract factories. Both ends look at two halves of the same order: operations watch states and stock, factories watch steps and pay.
| Module | What is inside | Who uses it |
|---|---|---|
| Order centre | Per-platform order columns, six-state flow, colour-coded first/second/third orders for new SKUs, batch label fetch, split-and-merge inspection reminders | Operations: every synced order from review to shipment on one line |
| Purchasing | Plan purchases and order purchases on two tracks, source tags on every PO, each buyer sees only their own POs | Buyers: turn ERP purchase plans into POs to factories |
| Warehouse stock | Inbound, available and reserved ledgers; product-code labels for bulk inbound; cancelled orders release stock and notify the PO | Warehouse: books match reality, every lock and release has an owner |
| Reconciliation | Supplier ledgers filtered by condition with editable fines and deductions (kept on record); carrier bills imported against per-carrier pricing rules | Finance: purchase cost and freight cost checked from both ends |
| Logistics config | Carrier lead times, estimated arrivals, non-serviceable ZIP areas, best-carrier recommendation per shipment | Operations & warehouse: choose the route before shipping, not by gut |
| Statistics | On-time delivery rate, platform return rate, order handling volume | Management: supply-chain health on one screen |
| Supplier end | Process configuration with unit prices, four order states (to review / in production / to deliver / done), mandatory scan shipping, after-sales returns, piece-rate pay, monthly ledgers | Contract factories: take orders, produce, deliver and get paid in one place |
| Roles & permissions | Internal and external staff configured separately by position and rank | Everyone: who sees and edits what is a config decision |
One design worth naming: suppliers must scan to ship — without a scan, the shipping step does not exist. That is not a UI constraint; it is the data premise. Shipping time, shipper and photos all come from the scan, and piecework, reconciliation and scoring are built on it.
Order Journey
From ERP sync to scan-to-ship, one order walks six stages. The point is that none of the six stages leaves the platform, and each leaves a record the next one can query.
The first three orders of a new SKU are where things go wrong: the process is not understood, the sample is off, the factory misreads the spec. These three orders get distinct colours — and the colours appear inside the supplier's own system.
The purpose is not decoration; it is a system-level reminder to work carefully on first production. Once the SKU settles down the colour fades, and the supervision cost drops to zero.
Labels come from the ERP and carriers, and they are not always fetchable. If unlabelled orders hide inside “to ship”, the warehouse discovers the problem at the moment of shipping.
So the six states include “label not fetched” with batch fetching: the pure interface action of pulling labels is split from the physical action of shipping, and the warehouse always has a label to print. States are fine-grained because each state maps to one action by one person.
Inventory
Cross-border stock goes stale fastest: purchases are on the road, orders hold goods, cancellations have not been released. The platform splits stock into inbound, available and reserved — three ledgers, each entry traceable.
Releasing stock on cancellation sounds obvious, but release means the goods re-enter the sellable pool — and if the cancellation is still being processed, auto-release may free goods that should not be sold.
The final design is auto-release plus PO notification: no manual gate, because “forgot to release” is the stealthiest form of stock drift. The risk is covered by notifying the buyer, who can stop the factory at once.
Received POs are visible only to the buyer who placed them. That is not permission purism; it is accountability: with dozens of POs per supplier and several buyers, a late delivery points at one person immediately.
Combined with on-time-rate statistics, supplier performance and buyer actions line up — the permission model and the scoring model share one partition, so the system never keeps two versions of the truth.
Supplier Scorecard
How do you decide which of dozens of factories deserves more orders? The platform turns the answer into a 100-point scorecard: eight indicators, each with its own formula and weight, scored monthly — the same result whoever runs the numbers.
Marketplace returns typically land one to two months after shipping: goods sent this month only start coming back next month. Score returns in the current month and you grade work the market has not yet tested.
So the scorecard runs two readings: a live reading looking back two months to today for daily watch, and a snapshot reading closing at the end of the previous month for monthly scoring. One dataset, two views, no argument at month end.
The supplier end has a dedicated rework analysis: a list queryable by time, process step and person, every rework carrying a reason, the reason tied to a process step, the step tied to a person.
Those two fields turn “this batch had many reworks” into “this person at this step had many reworks”. Piecework pays by scan; rework chases by step — earning more and being held to account use the same data, which is why factories accept it.
Reconciliation
For a supply-chain service company, the margin lives in reconciliation: purchase cost against suppliers, freight cost against carriers. Both lines are filterable, editable, and always on the record.
| Line | How it works | What it solves |
|---|---|---|
| Supplier ledgers | Orders produce ledgers per supplier, filterable by condition; entries can be edited (fines, deductions) with the change kept on record | Purchase cost with evidence: which order, to whom, how much, why deducted |
| Carrier bills | Each carrier's pricing rules configured in the system; carrier bills imported and matched automatically against platform shipment data | Freight drift caught within the month: over- and under-charges traceable per shipment |
Fines, deductions and compensation are negotiated outcomes; hard-coding them is unrealistic. What matters is that every change leaves a record: who changed it, by how much, on what grounds.
The ledger is then both a settlement basis and an arbitration record. Finance receives not one final number but the whole chain from order to amount.
Each carrier's lead time and non-serviceable ZIP areas are configured; the system recommends the best carrier per destination and time constraint. The logic lives in configuration, not in code.
Carrier prices and coverage change constantly — with rules in config, switching a carrier is one config change, not a release. It is also the premise of automatic bill matching: pricing rules are shared by both sides.
Deliverables & Results
The most direct change: the manual translation disappeared. Orders no longer get retyped from the ERP into purchasing spreadsheets, and suppliers no longer copy orders out of chat groups. Orders, purchasing and stock share one state machine — change one number and all three lines know at once.
The second change is on the factory floor: taking orders, work steps, delivery and pay all live in the mini-program. Scan records are both the wage basis and the scorecard's raw material — more output earns more, poor output is visible.
The third change is reviewability: on-time rate, return rate and the scorecard come out monthly, giving supplier grading and order allocation a shared set of facts. As agreed with the client, this page shows no client name and no screenshots of production screens; the third-party cross-border ERP is referred to generically.
If you are building cross-border fulfilment or factory collaboration — the platform takes orders, factories do the work, both sides reconcile — the hard parts are rarely the order page. They are the state machine, the stock definitions and the reconciliation rules. We have ground these down on supply-chain projects; bring your flow and we will tell you which one is your bottleneck.
MORE CASES
A supplier delivery management system: prices customised per customer group, with different customer...
View Details →A supply-chain service provider for cross-border apparel sellers: shops live on Amazon and other ove...
View Details →An all-in-one internal management platform for a bookkeeping and fiscal-service company: customer pi...
View Details →Start with our pricing logic, then let's talk requirements — cost structure, technology comparison and acceptance criteria, all laid out in the open.