Written by DROPS.ST.
A website explains the business, an online menu helps customers inspect products, and an ordering system captures a purchase. A point-of-sale system handles defined retail operations, which may include inventory and reporting duties in your market. One product can cover several jobs, but the labels do not prove that it covers all of them.
DROPS combines the customer-facing catalogue, checkout, order status, accounts and follow-up. Evaluate it for those jobs. Do not assume that buying a shop replaces a regulated POS or establishes a connection to a tracking system.
Map the work before comparing the names
The useful question is who handles each step and which record the team relies on. A brochure website with a menu link and a fully connected online shop create different amounts of work even when both are called a “dispensary website”.
| Job | Typical customer-facing tool | Operational question |
|---|---|---|
| Explain hours, service and shop identity | Website | Who keeps public information current? |
| Show products and prices | Online menu or catalogue | Which source determines availability? |
| Capture the selected items and details | Ordering system | When does an order become accepted? |
| Show payment and order progress | Commerce and payment services | Which status is authoritative for staff? |
| Record an in-store sale | POS | How does it affect available stock? |
| Provide required regulated reporting | Relevant operational system | Which supported integration and process apply? |
The last row depends on your jurisdiction and business. Establish it with the appropriate specialist and providers instead of inferring it from a software category.
Treat integrations as actual behaviour
Metrc's integration explanation describes how POS and operational systems can connect through its API for sales and inventory reporting. That illustrates a separate integration relationship. It is not evidence that every POS or website connects, or that DROPS has a native Metrc connection.
For any proposed connection, show the exact products, stock changes and order events it handles. Ask what happens when a request fails or a product identifier differs between systems. An integration logo is less useful than a demonstrated sale and correction with a clear owner.
Do not add a second manual stock ledger simply because two tools exist. Decide which system owns the stock count and how the shop receives a reliable sellable quantity.
Follow one order across the boundaries
Imagine an illustrative pickup order for two items. The customer sees both as available, selects a collection option and receives an order reference. Staff then identify the order, confirm the relevant status, allocate stock and prepare the pickup.
Now ask where each event is recorded. Does an online order automatically appear in the POS, or does staff enter it? When is stock reserved? What stops the same final item being sold in-store before the online order is handled? If the customer changes the quantity, who updates the affected records?
A manual handoff can be workable at a small volume when it is explicit and timely. It becomes a problem when everyone assumes another system has already completed it.
Buy the missing capability
If customers cannot order without messaging staff, the immediate need may be a clearer catalogue and checkout. If customers can order but stock is routinely wrong, the priority may be the source and timing of inventory updates. A redesign alone does not solve the second problem.
Our guide to POS and website menu accuracy explores those stock boundaries. Use shop software requirements to compare the exact jobs in scope.
Explore DROPS with one ordinary order and one stock conflict. See the customer journey, the order your team receives and the operational handoff it requires. Choose software that fills a clear business need and fits the systems your shop must retain.