Which supplier date can purchasing use in a customer update?
Format: Article.
Use a supplier date only when you can show who gave it, what it means, and how many units it covers. “Requested for Friday” is not “supplier confirmed Friday.” A planned ship date is not a warehouse receipt. Even after goods arrive, staff may need to check them before they can ship to a customer.
You can share a tentative date if you call it tentative. A planning date is useful. The mistake is to make it sound firm when the source does not. Keep the source's limits in the message, even if that means telling the customer you do not yet know.
Keep the date meanings separate
Use four plain labels in your purchasing notes:
- Requested: What your team asked the supplier to meet.
- Supplier stated: Who gave the date, what they said, and whether it means ship or arrival.
- System calculated: A date worked out from plans, workdays, and expected lead times.
- Warehouse recorded: What arrived, how many, where, and when staff logged it.
Microsoft Business Central can work out purchase dates from planning inputs. These include the requested date, supplier lead time, time to handle incoming goods, and a safety buffer. The Expected Receipt Date can be a planning result, not a supplier promise. [S05] Check what the field means before you quote it to a customer.
Build a supplier-date evidence record
| Field | Required entry |
|---|---|
| Item and supply reference | Exact item, supplier line, and receiving location |
| Quantity covered | Full line or named partial quantity |
| Date and event | The date, time zone if relevant, and dispatch versus receipt meaning |
| Source | Supplier contact and message, portal record, or system calculation |
| Source time | When the source was issued and when staff checked it |
| Confidence wording | Confirmed by supplier, tentative, calculated, or unclear |
| Revision link | Earlier date replaced and explanation provided |
| Customer use | Approved wording, reviewer, and review time |
A “confirmed” label should say who confirmed what. If a supplier says “Friday looks possible,” keep those words. That is a tentative date. A shorter note must not make it sound like a firm promise.
Hypothetical example: a partial filter shipment
A fictional distributor requested 80 filters by June 12. The planning screen shows June 12. The supplier later writes that 30 filters are scheduled to leave its warehouse on June 14. The remaining quantity has no confirmed date.
Do not tell the customer, “Your 80 filters will arrive June 14.” The supplier only named 30, and June 14 is when they plan to ship them. No source here says when the customer will get them.
A draft says: “Our supplier plans to ship 30 filters on June 14. We are still checking when they will arrive and when the rest will ship. We have not confirmed your delivery date.” Sales checks the draft against the promise already made. Then they decide whether to offer a part shipment.
When the warehouse logs that delivery, add the event to the record. Keep the supplier's first message too. Staff can then see both what was promised and what arrived. One should not replace the other.
Handle revisions without losing the reason
Save a new version when the date, count, or event changes. Mark which old statement it replaces. Keep both source messages and name the reviewer. A file uploaded today may contain last week's promise. Its upload time does not make the promise new.
When two supplier contacts disagree, keep both messages. Ask the purchasing owner to check with the person allowed to confirm that supplier's dates. Do not pick the answer that sounds best. If the date has passed but no event is confirmed, flag it for a check. Do not move it to tomorrow on your own.
Name who will follow up and when. Give customer care a time for the next check even if there is no arrival date yet. A promise to check is not a promise that the goods will arrive then.
Approve the customer message separately
Purchasing checks the supplier's facts. Warehouse staff check what arrived and what is ready to ship. The account owner approves a changed customer promise. Keep those roles clear, even if one person does more than one job.
A proposed custom system could gather supplier updates from approved sources. It could keep each version and link draft questions to it. It should not guess an arrival from vague words or change a customer promise without approval.
Core Agentic builds custom AI software to fit your purchasing and service tools. Access to a supplier portal or business record needs permission and tests. Staff would still check what each date means. This is not a live supplier connection or a service that predicts arrivals.
Bring an anonymized date conflict to explore a clearer purchasing-to-support handoff. Book a Demo.
Sources
These sources describe the named provider or framework. They do not establish a Core Agentic integration, customer result or certification.