A B2B customer orders 300 units over WhatsApp, approves the commercial terms, then asks for 100 units at one branch this week and the balance across two branches next month. The issue is no longer a missing shipping address. One commercial order now requires several separately confirmed deliveries.
Separate the agreement from the delivery schedule
The agreed quantity, price and commercial terms form the order. Allocation by site and date forms its execution plan. When everything lives in one informal chat message, a warehouse may interpret the total as one shipment or sales may overlook a branch that has not received its allocation.
Microsoft's delivery-schedule documentation describes splitting one commercial order line into multiple delivery lines with distinct quantities and dates. The principle can also be implemented in a carefully managed spreadsheet. It does not establish that Mr. AI creates warehouse schedules automatically.
Build a simple schedule before promising delivery
For every destination, record the site, city, receiving contact, allocated quantity, requested date and operations-confirmed date. Add packaging or site-entry requirements where relevant. Keep the total ordered quantity in the order header and reconcile it against the sum of delivery lines before sending confirmation.
Consider a hypothetical supplies distributor serving a retail chain. The customer requests 100 units for branch A, 120 for branch B and 80 for branch C. The total is 300, but agreeing on the quantities does not mean every date is feasible. Warehouse and transport teams must confirm capacity for each destination.
Three situations call for different messages
Sites and quantities are known, dates are not: Acknowledge the proposed allocation, but label dates as pending operational confirmation.
Allocation changes after approval: Review inventory and preparation work, then record a new schedule version and its approver. Do not erase the prior decision history.
One site has received its goods, others have not: Do not mark the entire order as delivered. Track each shipment independently and communicate what remains outstanding.
Microsoft's guidance on requested and confirmed shipment dates explains how transport time and warehouse calendars affect dates. This is a general system example, not a guarantee about Egyptian carrier schedules.
A confirmation message that prevents misunderstandings
"We have your allocation across the three branches. Our operations team will review each site's delivery date and return a confirmed schedule with quantities and dates. The total order quantity is unchanged, but the delivery dates are not yet approved."
Once approved, send one clearly dated schedule version. If the customer requests a change, obtain confirmation of the revised version instead of relying on scattered messages. If the change affects freight cost, revisit our quotation and delivery-address guide. Changes to the agreed commercial quantities may require a separate purchase-order revision process.
Give each decision an owner
Sales clarifies the buyer's request. Operations confirms feasibility. Finance reviews any pricing or invoice effect. The customer approves the final schedule. The person answering the chat should not invent a delivery commitment just to close the conversation quickly.
Review schedule changes after confirmation, destinations without completed receipt and mismatches between delivery-line totals and the original order. These are more useful operational signals than the number of acknowledgments exchanged in chat.
Mr. AI's role and limits
Mr. AI can help structure intake questions, answer from approved information and preserve conversation context for a human handoff. Do not assume warehouse, carrier or live delivery-status integrations without verified setup. Test the scenario in the customer experience or discuss it in a demo.
