What click and collect means for merchants
Click and collect is when a customer places an order online and picks the goods up in a physical store. For the customer it is a convenient and usually free pickup. For the merchant it is an operational flow where multiple systems need to coordinate in ways they were not always built for.
The physical store takes on a new role. It becomes a sales channel and a pickup point. It also becomes a small fulfilment hub for picked orders waiting for collection.
Staff need to see which orders are due to be picked. They also need to know which stock pool to pull from and when the order should be ready. The ecommerce platform in turn needs accurate visibility into what is actually on each store's shelves. A central warehouse figure is no longer enough.
What systems need to talk to each other
Click and collect requires multiple systems to share the same view of reality. Five systems are typically involved:
- Ecommerce platform — shows stock and accepts the order.
- Point-of-sale (POS) — handles the in-store pickup and, if applicable, payment at collection.
- Inventory or warehouse system — reserves the goods and tracks per-store stock levels.
- ERP — closes the order financially and handles invoicing or refunds.
- Notification system — keeps the customer informed from order placed through to pickup confirmation.
For merchants already running an established ERP like Fortnox or Business Central, the work is about letting those systems remain master and building the connections around them.
For the WMS question, it comes down to whether the warehouse system can split inventory by store. For order management, a click and collect order has a different lifecycle from a regular delivery order.
The reservation problem
When a customer places a click and collect order, those goods must not be sold to anyone else. That sounds obvious but it is where many implementations break down. If the in-store register continues to show the item as available and sells it across the counter, the ecommerce customer has a problem.
How this is handled depends on inventory partitioning. Either the item is reserved against the same physical stock the store sells from, which requires the POS to honour the reservation in real time. Or click and collect inventory is held separate from open store stock, which requires discipline in stock movements. Both approaches work but place different demands on the systems involved.
The reservation timeout is a parameter to decide early. Common windows are:
- 24 hours: suits merchants with high turnover
- 72 hours: the common window for consumer retail
- One week: used where pickup cycles are longer
The longer the reservation, the more capital is locked up, and the higher the risk that goods sit unused when another customer wants them.
Checkout integration and payment timing
There are two main paths for handling payment on a click and collect order. Either the merchant charges in checkout, which is the most common pattern today. Or the customer pays at pickup in store, which is more common in B2B and with merchants running higher order values.
When charging in checkout, the standard rules of the payment provider apply. Common Nordic providers all handle the scenario:
The important detail is that the receipt from the payment provider and the receipt from the in-store register must not conflict. The customer should not receive two separate receipts for the same purchase.
When charging at pickup, the ecommerce side marks the order as unpaid. The POS then takes payment like any other in-store sale. That requires the POS to be able to take payment against an already-picked order, which every modern POS can handle but which must be configured.
Notification flow
Click and collect lives or dies on customer communication. A customer who does not know whether the goods are ready becomes a customer who does not appear.
The notification flow typically consists of four events:
- Order placed: the customer receives confirmation that the order has been received and an estimated readiness time
- Ready for pickup: sent once store staff have picked the order and moved it to the pickup location
- Picked up: sent when the customer collects the goods, acting as a receipt
- No-show reminder: typically sent 24 hours after the order is ready, with a follow-up at 48 hours
In practice these notifications often originate in different systems. The first comes from ecommerce. The second comes from the POS or WMS. The third comes from the POS, and the reminder from a separate marketing tool. Maintaining a consistent voice and sender identity across the chain takes planning.
Platform fit
The four platforms Nordic Web Team works with handle click and collect in different ways:
- Shopify with Shopify POS has the most ready-made integration out of the box. For a D2C merchant with a small store count, it is fast to get started. As stores grow or as inventory and payment flows get more complex, third-party apps and customisation usually come into the picture.
- Magento with Hyvä has native multi-source inventory and click and collect support through Magento Order Management. It is powerful for merchants with many fulfilment points but requires more configuration up front.
- Norce with a headless frontend on Frntkey gives full API access to per-location stock. The click and collect flow is built as part of the storefront architecture.
- Shopware handles multi-channel and B2B flows well. Click and collect is possible but typically requires development work to wire up to Nordic POS systems.
The platform choice itself is rarely the blocker. It is how the other systems work together that determines timeline and budget.
Common pitfalls
Three problems show up in almost every click and collect project:
Per-store stock visibility. Many merchants only show a single central stock figure on the ecommerce side. Adding click and collect requires breaking that figure down by store location. That in turn requires accurate per-store stock counts. For merchants with weak stock discipline, this becomes apparent the moment click and collect goes live.
Handling no-shows. When a customer does not pick up within the deadline, what happens? Is the item returned to stock automatically? Is the payment refunded? Does the store keep the picked order for another period? This is a policy question that often falls between teams and creates manual work for store staff.
Returns at the pickup point. When a customer picks up and the item is not as expected, does the return happen in store or via ecommerce? If the store takes the return, the POS needs to handle it without necessarily knowing that it started as a click and collect order. That requires the POS to have access to the order history.
When click and collect is worth it and when it is not
Click and collect is worth doing for merchants that already have stores with staff who can pick. It also requires an inventory model that supports per-store stock. Finally, it needs a customer base that actually wants pickup.
For apparel chains it is now close to a hygiene factor. The same applies to sport and outdoor retailers and home and interior brands. Building materials and consumer electronics sit in the same field.
Click and collect rarely pays back for warehouse-only sellers without a store network. It is also questionable for merchants with very low average order values, where the pickup costs more than it saves on shipping. Merchants that already have inventory accuracy problems risk amplifying those problems rather than fixing them.
Timing of the rollout matters too. Adding click and collect during an ongoing platform migration or ERP integration project is usually a bad idea. Better to sequence the work.