Delivery or collection: a choice that changes the rest of an order
Connect fulfilment choice with location, availability and the next step without losing the order when a customer changes method.
Article language: English

In this article
A customer chooses collection because they pass a shop on the way home from work. “Centre” appears in the list. Only in the confirmation do they discover that it means the centre of another city and that the product will arrive there in a few days. The button worked. What they had actually chosen was still unclear.
How a customer receives an item is not a decorative field at the end of a form. It affects availability, the information needed and what the customer must do after ordering. The design should connect these details into one understandable decision. A switch with car and shop icons is not enough if both options lead through the same unrelated questions.
A collection point is a specific place
A location name should identify it unambiguously. Add the city, address and information needed to distinguish similar points. A company's own names may stay, but customers need not know its internal geography. Branches called “Main” and “New” mean something only to someone who knows when they opened.
A map can help, but should not replace a list. When designing a map of points with an equivalent location list (in Polish), check that both routes show the same places and preserve the selected point. A visitor may know the address and want to choose it quickly. They may also use a keyboard or have a connection on which the map loads slowly. Name, location and basic conditions should remain available independently of an impressive view of markers.
Do not require automatic device location to show all points if the function does not need it. A permission request can help find the nearest place, but the experience should still make sense after refusal. Allow entry of a city or browsing the list manually. A customer may be buying for someone in a different city from the one where they are standing.
Before design, distinguish the company's own point, a partner-operated location and other handover methods. They may need different information and readiness confirmation. Do not combine them under one label merely because all end with the buyer appearing in person. Agree who actually prepares and hands over the product, and where the message comes from.
When describing time, establish when counting begins. “Collect in two days” can be understood differently if preparation starts only after an order condition is confirmed. Your own example should reflect the company's real rule, including working days and the hours during which orders are accepted. Do not add specific dates for a mock-up if nobody has approved them.
Relative words also need updating. “Today” on a page left open for a long time should not continue to describe the following day simply because the page was idle. Decide when information refreshes and what the system must confirm before accepting the selection. The screen should explain the current possibility rather than retain an old promise beside a current button.
At each point, distinguish opening hours from the time needed to prepare an order. A shop can be open today while the item is ready tomorrow. These details should work together. “Collect during opening hours” does not answer when the purchase will actually be waiting for the customer.
Show practical conditions the company can confirm: the entrance, required check-in or instructions for that specific point. Do not copy another location's description. For long addresses and names, use principles for displaying long text (in Polish) so a narrow screen does not cut off the part that identifies the place.
Company-wide stock does not yet answer “where and when?”
A fictional order contains two different products. One is in the chosen shop, the other in the shipping warehouse. The customer may be able to collect them together later, change the point or choose another fulfilment method. That depends on the company's real workflow. The interface should show an agreed option rather than compress the whole organisation's availability into one green word.
Shopify describes transferring stock to a collection point and a separate preparation time for such an order. This is an example of one platform's mechanism. For the design, the key is to identify whether the selected location has the item on site or needs an extra step before handover.
If a transfer is needed, give the customer the resulting date or explain what the company can confirm. Do not present it in the same way as something ready for collection. The buyer may be choosing the method because of timing. Revealing the difference only in a message after purchase removes the chance to compare knowingly.
Availability must refer to the correct variant. Colour, size or set may have stock in different places. After a product change, check whether the earlier location can still fulfil the task. Preserve the selection where it remains valid; if there is a problem, explain what needs to change. Do not move collection to another city without a noticeable customer decision.
Principles for communicating unavailable stock (in Polish) help distinguish an absent item, an unconfirmed state and availability only at a particular place. If the system cannot currently check a location, that does not automatically mean every product is absent. This state needs its own message and a way to retry.
A visitor may start with a location on the product list. A filter showing items available at a point helps orientation, but its scope must remain understandable. In the shop filter design (in Polish), state whether it means collection after preparation or stock already on site. Do not give different promises the same label.
Decide whether an order can be split between methods. If it can, show which items belong to each part. If it cannot, explain the limit before the final choice. Do not let customers see several possible points for individual items only to discover at the end that the entire basket has no common option.

Showing a split in a mock-up does not prove it is supported. Staff must be able to locate the parts, prepare appropriate messages and confirm handover. More options also mean more order states. Agree the integration scope before pricing and implementation so the screen reflects the company's real capabilities.
Changing the method should change the questions asked
A customer starts with shipping and enters an address. Then they notice a convenient collection point. Must they enter everything again? Does the shipping address disappear, or does it remain marked as required? A good path allows a change of intention and clearly shows which information is still needed for the chosen fulfilment method.
WooCommerce's block-based local pickup allows a point to be selected without entering a shipping address. This is the behaviour of a particular version of the feature, distinct from the older pickup method. It illustrates a simple design question: why require information not used in this path?
Do not automatically delete previously entered information if it may help when returning to the earlier method. At the same time, do not let a hidden old field continue to block progress. Requirements and messages must match the visible choice. Customers should not have to search for an error in a section the screen no longer shows.
Distinguish the recipient, buyer and contact for questions if the process actually requires it. Do not add all those roles just in case. Ask staff which details help prepare an order and which merely duplicate the existing form. In form design (in Polish), the purpose of each field is a good starting point for that discussion.
When changing a place, check cost and conditions too. If the total changes, show it before the next confirmation. If it cannot yet be calculated, explain which information is missing. Do not leave an old amount beside a new location in a way that suggests all details have already been recalculated and accepted.
On a phone, the list of points should not indefinitely cover the selection summary. Customers need to see the chosen place and a way to change it. Long instructions may be expandable, but the address and basic collection condition should remain easy to check. Order fulfilment depends on them.
For an external point selector, make sure there is a return to the order. The user should know whether the location was accepted and still relates to the current basket. Closing a map or additional window must not require guessing the outcome. If the choice did not save, show the lack of confirmation instead of pretending the decision is complete.
Consider an empty list too. It may result from the location, a particular product, service hours or a loading error. Not every cause can be resolved by entering another city. The message should match the known state and suggest an action that can actually help, without automatically deleting the remaining information.
After purchase, the customer needs to know what they are waiting for
Receipt of an order and readiness for handover are different events. If a message says only “thank you for your purchase”, a person may take it as an invitation to travel. Say whether they should go to the point now or wait for a separate confirmation. The correct signal should reflect the preparation state, not merely a form being submitted.
On the confirmation page (in Polish), retain the point's name and address and the stage that has just been accepted. The customer may close their email or not receive a message immediately. The screen should already make the next path understandable and show where to seek help if the next confirmation does not arrive.
Collection instructions must concern the correct place. Hours, a rear entrance and contact method can differ by location. Do not assume one template with the branch name substituted will be enough. The needed information may come from a locations model that supports exceptions without manually correcting every message.
Connect communication to the items and order version. If part has shipped and part awaits collection, a general “fulfilled” status may not explain the situation. Where the shop supports such a split, show it in messages too. Agreed transactional messages (in Polish) should guide customers through real stages, not merely carry the same logo.
Plan for a change on the company's side too: a point may temporarily stop accepting collections or preparation may be delayed. The message should identify the order, previous choice and what has already been confirmed. Do not present a proposed alternative as a decision the buyer previously made. A clear path to agreeing a new fulfilment method is needed.
If only one part is delayed, show its relationship to the rest. Does the whole order still wait, or can the other items be collected? The answer must come from the agreed operation, not a generic delay template. This is another place where communication design needs knowledge from the employee responsible for the actual handover.
Decide how to handle changes after ordering. A customer may request a different point, but the request alone does not change the confirmed place. Show how to contact the company and communicate the outcome of its assessment. Do not promise unrestricted changes in the interface if an employee must act or if changes are impossible at that preparation stage.
For acceptance, enact the purchase path for an item on site, one requiring transfer and one unavailable at the point. Change the method after entering information, then return to the earlier one. Check the result on screen and in a confirmation authorised for the trial. Each stage should describe the same location, item and promised next step.
Aeneia Design covers shop design and integrations within the agreed scope. Locations, preparation rules and example messages will help the conversation. “Centre” can then calmly help someone find the shop, without an expedition through the entire branch network.










