Match the exact item, not just its name
A shared product name is not enough to connect your records reliably. A blue mug and a white mug may sit under one catalogue heading, but staff need to distinguish them when counting, picking and updating availability. Record a consistent internal reference for each sellable option, then confirm how those references can be represented in your proposed setup.
Prepare a simple mapping sheet showing the shop reference, online listing, option, price and fulfilment restrictions. Treat descriptions and images as merchant tasks: check that the photograph, size, colour and pack quantity describe what the customer will actually receive. Do not assume an identifier automatically creates a link between systems.
- Select a few products, including one with options.
- Match each option to its physical item and shop record.
- Ask the team how identifiers and options are handled.
Decide what available quantity means
Physical stock and stock available to promise are different. Items may be damaged, awaiting collection or already allocated to an order. Decide which record staff should consult and when an item stops being available to another customer. This matters especially when the final unit could be bought at the counter and online close together.
Ask the NeroPay team whether your proposed combination of NeroWeb and shop systems supports stock updates, in which direction and at what point in the order journey. Establish any delay, exclusions and recovery procedure. If the required connection is unavailable, consider a separately allocated online quantity or a smaller online range, but only where your setup and staffing can support the necessary updates.
- Define which stock is saleable, reserved or unavailable.
- Confirm what happens after a shop sale, online order and cancellation.
- Choose a fallback process for missing or delayed updates.
Give every change an owner
A workflow needs a named role, not an assumption that someone will notice. Decide who changes descriptions, images, options and prices, and where each change starts. Separately assign stock adjustments for deliveries, breakages, returns and exchanges. A returned item should not become available again until someone has checked that it is fit for sale.
Write down the handover between taking an order and preparing it. Who checks availability, picks the item and records that it has left the saleable stock? If an item cannot be supplied, identify who contacts the customer and follows your agreed cancellation or alternative-item process. Keep customer communication consistent with the actual order status.
Test a last-item sale before widening the range
Hypothetical example: an independent homeware shop has six green mugs. One is damaged and two are being held for collection, leaving three available to promise. The retailer maps the green option to its shop reference and agrees how held items will be excluded. The online quantity is then set using the workflow confirmed for that retailer, not an assumed shared stock feed.
During testing, staff record a counter sale, check the online position and follow an online order through picking. They also test a cancellation and an inspected return. Success means the expected quantity can be explained at every stage, each order can be matched to the correct item, and staff know what to do if an update fails. An unexplained difference is a reason to pause and investigate, not expand the range.
- Record starting quantities and expected changes.
- Run agreed tests across both channels.
- Compare the records with a physical count.
Make collection and delivery promises practical
NeroWeb merchant setup supports collection and delivery settings, alongside custom-domain configuration. Decide which products suit each fulfilment method and write clear preparation expectations. A fragile item may need different handling from a boxed accessory. Confirm the available settings before promising a particular collection window, delivery area or ordering restriction.
Your next action is to take the mapping sheet, responsibilities and test results to the team. Confirm availability, supported systems and commercial terms before launch. With an eligible NeroPay card terminal, NeroWeb software can be included without an additional software subscription charge; terminal costs, payment processing charges, applicable delivery costs, eligibility and terms still apply.
GOOD TO KNOW
Common questions
Does NeroWeb automatically synchronise shop stock?
Do not assume it does. Confirm the actual behaviour for your proposed systems, including update direction, timing, supported events and what happens when an update fails.
Should every shop product be available online?
Not necessarily. Start with items staff can identify, count and fulfil reliably. Add complex options, fragile goods or scarce items once their handling process has been tested.
What should staff do if two customers want the last item?
Follow a pre-agreed allocation and customer-contact process. Check the order records and physical item before making a promise, and investigate why both channels showed availability.
What should I prepare before speaking to the team?
Bring your current shop system details, sample product references, option structure, stock responsibilities and collection or delivery requirements. Ask which parts are supported and which need manual handling.