Written by DROPS.ST.
An estimated time of arrival (ETA) needs an arrival date, source and unresolved conditions. “Friday” is incomplete if nobody knows whether it means dispatch, carrier arrival or a receiving window agreed with the buyer.
DROPS connects timing discussions with specific shop records. Catalogue units and wholesale packages define the quantity being discussed, while customer-linked order items preserve the buyer’s selection. Staff can identify the affected item and order instead of discussing a general availability message.
Supplier tracking, ETA fields and automatic updates are separate workflows to demonstrate; shared catalogue and order records do not establish native shipment tracking.
Name the event
Distinguish these milestones:
- Expected dispatch: when the supplier thinks the shipment will leave.
- Confirmed dispatch: evidence that the identified shipment left.
- Estimated arrival: when a source expects it to reach the destination.
- Agreed receiving window: when the receiving business is prepared to accept it.
- Recorded arrival: when the shipment was observed to arrive.
A dispatch date is not an arrival date. An agreed receiving window does not prove the shipment can reach it.
Use the authorised commercial process for actual commitments. These labels describe operational evidence, not a contract’s legal effect.
Record the source and conditions
| Field | Record | Question answered |
|---|---|---|
| Shipment and line | Reference, item and quantity | Which goods? |
| Milestone | Dispatch, arrival or receiving window | Which event? |
| Date or range | Source’s date and time zone where needed | What was stated? |
| Source | Supplier or carrier evidence reference | Who supplied it? |
| Checked time | When obtained or reviewed | Still current? |
| Conditions | Missing confirmation or dependency | What could change? |
| Next review | Owner, question and review time | Who checks next? |
Preserve a range rather than replacing it with the earliest date because that is easier to plan around.
The UK Government Data Quality Framework recommends clear information about data quality and documentation that reduces ambiguity. Source details and unresolved conditions help colleagues understand what they can rely on. Government Data Quality Framework.
Label the evidence without inventing certainty
Use simple internal labels:
- Awaiting source: no timing evidence received.
- Source estimate: dated expectation with identified conditions.
- Event evidenced: a milestone supported by evidence.
- Exception open: an earlier milestone or date needs reconciliation.
- Arrival recorded: receiving staff have recorded the identified shipment.
Evidenced dispatch strengthens what you know about dispatch. It does not make the arrival estimate certain.
Use numerical confidence only with a measured basis. A confident supplier conversation does not justify “95% certain.”
Separate the plan from the commitment
Staff may plan labour around an estimate. That does not authorise promising the same date to a buyer.
Identify who may make or revise a commercial commitment. Give them the source, milestone and conditions rather than a date alone.
BDC’s inventory guidance recommends transparency about lead-time requirements. That supports explaining the timing basis instead of hiding uncertainty behind an unexplained date. BDC: lead times and inventory.
Use the approved business channel; this guide does not establish messaging-provider permission.
Hypothetical example: dispatch becomes an arrival promise
On 3 November, a fictional supplier expects to dispatch item A on 5 November. A sales colleague tells the buyer to expect arrival on 5 November.
The record exposes the difference: the source gave a dispatch estimate, but the buyer received an arrival statement. No carrier arrival evidence supports it.
The responsible person clarifies the commitment and obtains the missing information through the approved process. They preserve the earlier communication rather than rewriting history to make the promise look supported.
Evidence of dispatch on 5 November would close the dispatch question. Arrival remains a separate question.
Review changes and shop consequences
Choose review triggers such as a missed dispatch estimate, revised carrier range, incomplete confirmed quantity or changed receiving availability.
Identify the affected line, order, responsible person and missing fact. Do not change every account’s message because one shipment has an exception.
Keep an old estimate distinguishable from its replacement. Record when the source changed and which plan needs review. An old screenshot should not become the current arrangement.
Expected incoming goods and available shop stock are different facts. Complete the required receiving and stock process before changing the catalogue. Use the menu accuracy guide if the checked source and customer view disagree.
For early requests, the wholesale enquiry guide captures the requested date without turning it into a confirmed commitment.
Give timing decisions context with DROPS
Choose DROPS when you want the buyer’s selected items and quantities linked to the customer and order. Named packages make the quantity explicit, while the shared website and connected Telegram order system keeps the shop context organised.
Explore DROPS and open the demo shops. Bring one fictional estimate and identify the catalogue lines and order it affects. Evaluate any required delivery fields separately, then keep timing evidence clear enough to distinguish an expectation from an authorised commitment.