Including business receiving hours in delivery choices

A business delivery location may be open on Tuesday but only accept goods between nine and eleven. A calendar showing only a date provides insufficient context. The online store needs to decide whether it can actually support such receiving windows or whether planning must first assess what is feasible. For Checkout & Delivery, business opening hours are therefore an operational agreement that goes beyond a free-text field beside the delivery address.

Ask about the restriction that determines delivery

In a fictional order, a company has furniture delivered to an office with a shared loading bay. The bay is available until eleven; other suppliers use it after that. The customer writes “early, please”. That note is too vague for planning. The store needs to know whether early is a preference or a firm receiving requirement. Design the question around that distinction and collect only information the team actually uses.

Distinguish general opening hours from a one-off appointment. Reception may be open all day while the warehouse accepts deliveries only by appointment. Ask the customer to explain which receiving point they mean. Then state what assessment will follow. If the store cannot promise a time slot, a submitted window must not be presented as an accepted appointment . The value lies in identifying a restriction early so planning can discuss a feasible next step.

Choose between supported windows and an assessment

For a defined application, you can support a limited number of business receiving situations. Describe the appropriate route for each: standard delivery, prior assessment or contact to arrange a separate appointment. The existing Yindle delivery component is based on date selection, capacity and changes. That does not establish a general feature for arbitrary business time windows. The required rules and connection to route planning need to be developed and tested for the individual store.

Discuss with planning what a time restriction means in practice. Does extra travel time need to be allowed? Can the team confirm the appointment manually? What happens when several customers request the same short window? A form cannot create that operational capacity. Start with one type of business restriction and check whether employees can process the request. Expand only when the selected information leads to useful decisions and customers understand the outcome.

Test the handover with three receiving locations

Use fictional locations: a warehouse with broad receiving hours, an office with a short window and a location that only receives deliveries by separate appointment. Ask an employee to go through checkout, then have a planner read only the order information. Can the planner see what is confirmed and what still needs discussion? Then ask support to explain the same arrangement. Conflicting answers indicate unclear labels or a missing handover step.

Define who contacts the customer when a window is unworkable and where the final agreement is stored. Keep the customer confirmation consistent with that agreement. For connecting the online store and planning, Yindle Connect is relevant. You can discuss the required exception route as part of custom software. The result is a business delivery request that identifies restricted receiving times early and only turns them into a promise once the store has actually assessed them.

For the classic order steps around a business delivery choice, read more about Yindle Checkout. Support for receiving windows and route planning still requires your own rules and acceptance tests.

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