Small manufacturers often track open purchases through a mixture of ERP reports, spreadsheets, email, calls, and messaging groups. A purchase order may show the original delivery date while the supplier has promised a later partial dispatch. Production sees the old date, stores sees nothing received, and purchasing carries the latest position in someone's notes.
Supplier delivery tracking software should create one current view from order acknowledgement through usable receipt. It should reveal which commitment changed, what work is affected, who is following up, and what decision is needed.
Track every purchase-order line
A header-level status such as “partially received” is too broad when an order contains several materials and dates. Track item, quantity, unit, required date, supplier-confirmed date, dispatched quantity, received quantity, accepted quantity, balance, and current status for each line.
Where one line is split into schedules, keep each promised quantity and date visible. This prevents an early small delivery from making the complete requirement appear covered.
Separate the important dates
Use distinct fields for the internal required date, purchase-order date, requested delivery date, supplier-confirmed date, planned dispatch date, actual dispatch date, expected arrival, actual receipt, and usable date after inspection where applicable.
These dates answer different questions. The supplier confirmation shows the current external commitment. The internal required date shows whether that commitment supports the factory plan. Preserving date changes also explains when risk first became visible.
Record supplier acknowledgement
After issuing a purchase order, confirm that the supplier accepted the item, specification, quantity, price terms already agreed in the order, delivery location, and required date. Record the acknowledgement date, confirmed schedule, contact, and any exception.
A missing acknowledgement is itself a risk. Use a clear status such as awaiting acknowledgement rather than treating silence as confirmation. Link the order back to the approved need described in the digital purchase requisition workflow.
Use precise delivery statuses
A compact status model may include awaiting acknowledgement, confirmed, due later, due soon, dispatch pending, dispatched, partly received, received under inspection, partly accepted, complete, delayed, disputed, cancelled, and closed. Define what moves a line between states.
Show the latest update time and owner. Avoid a generic “follow-up” status that does not reveal whether the supplier, transport, receiving, quality, or an internal decision is the current constraint.
Connect deliveries to production impact
A delayed component matters because it affects planned work. Link the open purchase line to the material requirement, reservations, production jobs, and customer commitments it supports. Compare the usable expected date with the job need date.
The guides to material shortage alerts and production planning software explain how supply dates affect projected stock and job sequence. Delivery tracking should feed that shared view instead of producing a separate purchasing-only report.
Handle partial delivery without hiding the balance
Record each dispatch and receipt against the correct purchase-order line and schedule. Show dispatched, received, rejected, accepted, and remaining quantities separately. If the supplier revises the balance date, preserve the previous promise and reason.
Production may be able to start with a partial quantity, but that decision belongs in the plan. The delivery tracker should show which jobs can be covered and which still depend on the balance.
Capture dispatch evidence and expected arrival
When the supplier reports dispatch, record dispatch date, quantity, transport reference where used, expected arrival, packing details, and any required documents. Attach evidence only when it supports receiving or traceability; do not turn the tracker into an unstructured document store.
Define who updates expected arrival when transport information changes. A line should not remain “dispatched” indefinitely without an exception when the expected arrival has passed.
Close the loop with receiving and inspection
Stores should record receipt against the order line, including actual quantity, date, location, package condition, and discrepancies. If incoming inspection is required, the material is not yet usable merely because it reached the gate.
Link the receipt to the digital quality inspection record. Show accepted, rejected, and held quantities so planning does not count blocked material as available.
Use one expediting workflow
- Detect. Flag missing acknowledgement, changed promise, due-soon risk, overdue dispatch, overdue arrival, or insufficient accepted quantity.
- Assess. Identify affected jobs, quantities, need dates, and available alternatives.
- Assign. Give the exception an owner and follow-up date.
- Contact. Record the supplier's updated commitment and reason without relying on private notes.
- Decide. Expedite, split, transfer, reschedule, source through an approved process, or revise the plan.
- Verify. Confirm dispatch, receipt, and usable quantity before closing the exception.
Keep the action connected to the purchase line and affected production. A standalone expediting spreadsheet quickly becomes another version to reconcile.
Design alerts that lead to action
Alert when a supplier has not acknowledged by the agreed follow-up point, a confirmed date no longer supports the requirement, dispatch evidence is missing, expected arrival is overdue, or accepted quantity is insufficient. Prioritise by production impact and time available to respond.
Group related lines and avoid sending the same unchanged warning repeatedly. Raise priority when the date slips, the shortage grows, or the action becomes overdue. Explain why the alert changed.
Keep supplier communication traceable
Record the meaningful outcome of calls and messages: contacted person, update time, committed quantity and date, reason, evidence, next follow-up, and owner. Do not copy every conversation into the system; capture the decision that changes supply or risk.
Use controlled reason categories such as capacity, material, quality, transport, documentation, specification clarification, or internal order change, with notes for context. Neutral, consistent reasons support later process review.
Review exceptions at a useful rhythm
Use a daily view for overdue and near-term lines affecting active work. Review unacknowledged orders, changed promises, incomplete dispatch, transport delay, receiving discrepancy, quality hold, and overdue actions. Each item should end with an owner and next date.
A broader weekly review can examine recurring supplier-date changes, acknowledgement delays, partial-delivery patterns, receiving discrepancies, and the quality of internal required dates. Add only actionable purchasing exceptions to the factory dashboard.
Build a fair supplier view
When reviewing supplier performance, compare against the agreed confirmed schedule and account for authorised order changes. Keep quantity and date definitions stable. Separate supplier-caused delay from internal specification changes, late approvals, or receiving and inspection delay.
Use the record to prepare factual discussions and improvement actions. A score without the underlying order lines and reasons can create more argument than insight.
Pilot one supplier or material family
Select a supplier or component family with active orders and regular follow-up. Clean open order lines, required dates, confirmed dates, units, outstanding quantities, and receiving status. Agree on statuses, alert rules, update ownership, and the daily review.
Test acknowledgement, full and partial confirmation, revised promise, partial dispatch, late arrival, excess or short receipt, inspection hold, rejection, replacement supply, cancellation, and closure. Run the pilot until purchasing and production can explain the same current position without a parallel sheet.
Begin with the orders your team chases manually
Choose a small group of open lines that currently requires repeated calls or messages. Map the required date, supplier promise, dispatch, receipt, inspection, affected production, and action owner. Identify where the current information becomes stale.
A focused supplier delivery tracker gives purchasing a clearer follow-up queue and gives production a more dependable supply date. Once that loop works, expand it to more suppliers, transport milestones, receiving locations, and supplier-development reviews.
Want a practical supplier delivery workflow?
Share one open-order report and the follow-up process your team uses with suppliers. Ploqy Technologies can help map a focused digital workflow around commitments, dispatch, receipts, quality status, production impact, and ownership.