One delivery date for items with different preparation needs

Include a customer who places their order on a preparation day in the trial too. This lets the team see whether the chosen rule accounts for its own sequence of work, rather than just a number of elapsed calendar days.

A customer chooses one delivery day for an order, even though the items need different preparation. An in-stock item may be ready tomorrow; a finished custom product takes longer. The online store must decide what commitment it can make for the order as a whole. For an application such as Yindle Checkout & Delivery, that starts with a clear rule for the order: which items determine when the order can be ready, and what happens if that information is missing?

Make preparation visible before showing the calendar

Take a fictional order containing standard panels and custom-finished edge pieces. The customer needs both for the same project. If the calendar only looks for an available delivery slot, it may offer an early date when the edge pieces will not yet be ready. The shop therefore needs to assess preparation and transport together. A free slot in the schedule is useful when the entire agreed shipment can be available on time.

Record which preparation counts for each relevant product group and who maintains that information. Distinguish between a fixed processing time and an uncertain supplier estimate. Showing a precise date based on uncertain input creates a commitment that planning cannot substantiate. Start with simple, explainable rules and identify where manual assessment is still needed. The existing Yindle delivery component offers capacity and temporary selections as a starting point; product-dependent preparation requires the shop’s policies to be configured appropriately.

Choose a commitment for the whole order

One combined delivery may be the clearest option for an initial implementation. In that case, the item that can be ready last determines the earliest feasible day. Write that rule in customer-friendly language and test whether it fits the range. Another shop may deliberately use several shipments, but that requires separate agreements and further development of the process. A calendar with one selected day does not demonstrate support for several independent deliveries.

Ask the team to talk through the mixed order aloud. When must production start? Who notices if a component will arrive later? May the customer still choose a day if preparation has not yet been confirmed? The answers determine which data is needed before the calendar. For exceptions, record an owner and a follow-up time. An order requiring manual assessment must not suggest a confirmed delivery commitment to the customer until that assessment is complete.

Check three baskets and one disruption

  1. Test a basket containing only immediately available items.
  2. Add an item requiring extra preparation and assess the new earliest delivery option.
  3. Remove that item and check whether the explanation fits again.
  4. Deliberately make the preparation information uncertain and assess the agreed next step.

Run the trial with fictional data in the intended checkout. Ask the planning team to check that the offered days align with the actual working agreements. Then review what appears on the order and in the customer confirmation. The selected day must mean the same thing to the customer everywhere. Yindle Connect is relevant for transferring data to planning; to design the complete ordering journey, you can discuss online store development. The result is a delivery choice that matches the readiness of the entire agreed order.

Previous insight
Next insight

Start with your question

Where does your team get stuck?

Your first enquiry does not need to be a technical brief. Tell us which systems you use and where work gets stuck. Together we discuss what is possible and which step you can take next.

Discuss my project