01
Publish an assortment the store can fulfil
Start with the products the team can describe, price and pack consistently. Check images, units and product variants so a customer knows whether they are buying a pack, a single item or a weight selection.
Tellency’s storefront includes category browsing, product search and supported weight-based quantity choices. The online assortment is controlled through the ERP. Test the exact units used by the branch so displayed quantities and packing expectations agree.
02
Define the delivery and pickup offer
Decide which areas are served, which branch fulfils them and what fee rules apply. Communicate minimum orders and available slots before the customer completes checkout.
The store configuration supports delivery and pickup choices, fees, minimum order values and time-slot rules. For pickup, verify the branch details and what happens when the customer arrives. For delivery, test both a served address and one outside the intended area.
03
Make availability changes understandable
A shelf can change between browsing and packing. Define the procedure for an unavailable item, a changed price or a quantity the store cannot supply. Decide what the customer may request and who confirms a change.
Use packing notes and supported customer choices where appropriate, but do not treat a note as permission to change the financial result silently. Demonstrate the actual exception workflow in the configured system and record any additional requirement in the implementation scope.
04
Give each order state a clear owner
Assign responsibility for accepting the order, packing it, marking it ready or out for delivery, and completing it. Customer order tracking should reflect those operational steps.
In Tellency, online order completion connects to the configured invoice, payment record and branch stock movement. Compare the accepted order with those records, including the delivery charge, before signing off the workflow.
05
Pilot the service before expanding its area
Use a manageable assortment and delivery area to test whether staff can meet the promised slots. Record order questions, packing errors and payment confirmation issues. Review operational evidence rather than assuming more online channels automatically improve service.
Once the process works, a customer-branded iOS or Android app can offer another route to the same store. Test its address entry, cart and tracking independently while retaining the shared ERP rules.
- Representative packaged and weight-based products.
- A delivery order and a branch-pickup order.
- A missing item or quantity correction scenario.
- A payment confirmation and completed invoice check.
- Matching customer status and branch stock records.
Questions to take into planning
Can Tellency support online grocery delivery and pickup?
The storefront supports configured delivery and pickup, catalogue browsing, checkout slots and order tracking connected to Tellency ERP. Demonstrate your assortment, units and branch process during scoping.
How should we test grocery products before launch?
Use representative packaged and weight-based items, check the displayed units and prices, place delivery and pickup orders, then reconcile the packed quantities, final invoice, payment and branch stock movement.