Written by DROPS.ST.
Bring the shop online by sharing dependable product facts and assigning ownership of online orders. Start with a manageable range, a clear stock rule and a realistic collection or delivery process. A second sales channel should not create a second, conflicting version of every product.
DROPS offers a mobile catalogue, checkout, order status and customer accounts, with assistance moving products, prices and images. That gives a physical shop a practical ordering path. Any connection to your existing POS needs its own confirmed scope and demonstration.
Reuse product facts, not undocumented assumptions
Your physical shop already knows the product names, pack sizes, prices and supplier references. Turn that knowledge into a consistent source for online listings. Check it before import: till abbreviations and shelf labels may be too compressed for someone shopping without a staff member beside them.
Separate shared facts from channel-specific information. The exact model and pack contents should agree across the business. A collection cutoff, online delivery fee or channel-specific offer may differ, provided the customer can understand the difference.
| Information | Shared across the shop | Online-specific responsibility |
|---|---|---|
| Product identity and pack contents | One agreed product reference | Clear name and description |
| Manufacturer compatibility | Same verified source | Visible explanation near the item |
| Price | Agreed pricing policy | Current displayed price and offer scope |
| Availability | Defined stock authority | Sellable online quantity or availability rule |
| Fulfilment | Shop's actual capacity | Collection or delivery promise shown at checkout |
This is a responsibility map. It does not claim that the information automatically synchronises between systems.
Choose how stock reaches the online menu
If a supported integration exists, demonstrate how an in-store sale changes online availability and how an online order affects stock. Check timing, cancellations and the final item in stock.
If the process is manual, make it explicit. A limited online allocation or a small initial range can be workable when someone keeps it current. Set a review rhythm that matches sales activity rather than assuming yesterday's count remains accurate all day.
Our guide to POS and menu accuracy helps define which stock record is authoritative. Do not promise branch-level inventory or real-time synchronisation unless your actual setup proves it.
Give online orders a place in the working day
Decide who notices an order, who checks its status, who picks it and who tells the customer it is ready. The person serving the counter may not be able to monitor a second queue continuously during a rush.
Consider an illustrative pilot with 20 online products and two collection windows. The opening shift checks availability; one assigned person reviews incoming orders at agreed intervals; the closing shift reconciles anything still waiting. These are proposed operating choices, not automatic DROPS timers.
Make the collection promise fit that process. A customer who sees “ready” should receive the same answer from whoever is at the counter. Avoid sending readiness messages before the order has actually reached that stage.
Start with the range you can maintain
Choose products with clear identities, stable information and enough stock visibility to support the pilot. Include one item with choices and one multipack so you discover naming and quantity issues early.
DROPS customer accounts and order history can help staff answer online order questions without searching several chats. Inspect the exact staff view in a demo and decide what access a covering employee needs.
If you already have a website, connecting an existing site to a shop covers the customer route into ordering.
Explore DROPS with your pilot range and a normal shop shift in mind. Build the online channel around shared facts, clear responsibilities and orders your team can fulfil confidently.