How to prepare an online shop: catalogue, orders and purchase tests

An online shop needs to connect its catalogue to its operation: the product chosen must match what is charged for, prepared and delivered. Design is one part of the work. This guide organises data, responsibilities and tests so that the first order is not the first time the team follows the complete process.

By Lyntev. Updated on .
About 7 minutes to read.

A request that stays connectedThe same reference follows the request and prevents duplicates.

Translation published on . Original Portuguese guide; source revision .

By the end, you can:

  • Define products, variants and stock
  • Separate orders, payments and delivery
  • Test purchases and exceptions before publishing

Define what you will sell and where it can be delivered

Start with a catalogue the team can maintain. Identify physical products, services or digital content, because they need different journeys. Record delivery countries or regions, currencies, payment methods and operational dependencies. Only show an option if there is a process for carrying it out; do not offer international delivery without confirming transport, costs and relevant conditions.

Separate launch requirements from future features. A shop can begin with well-prepared categories and add advanced filters or loyalty programmes later. Before choosing a platform, describe variants, stock, orders, invoicing and integration with current tools. Compare your needs with the plan’s actual features and recurring costs, without assuming every module is included because a button appears in the design.

Take an item you sell today. Can you immediately state its final price, availability and delivery cost to the customer’s address? If a made-to-measure item needs design, measurement or a transport quote, a catalogue with a quote request may suit that first stage better. Reserve direct purchasing for items the team can actually sell under those conditions.

When comparing proposals, note the total cost of getting sales working and what you will pay to keep the shop open. At Lyntev, creating a template-based online shop starts at 600 €, including adaptation to your brand. List the domain, payment-provider fees, delivery charges and any recurring services separately. Ask for the conditions of each for the order volume you expect.

How do you test the connection between the shop, stock and invoicing?

Take a real variant to the demonstration. Ask to follow it from the basket to the invoicing software and back to the order that generated it. In the connector between WooCommerce and Moloni ON, for example, the product reference in Moloni ON must match the SKU in WooCommerce. The SKU is the code distinguishing an item or variant. Also confirm in which program the team can change prices and quantities, and in which direction those changes propagate.

The table is a fictional test to request from the supplier in a test environment. The Mesa Clara shop starts with two blue cups and two white ones. The blue reference is MC-AZ-01 and the white reference is MC-BR-01. In this scenario, only confirmed payment permanently reduces stock. Record the result in the shop and the management system after each step. Rules for issuing documents, handling returns and restocking need to be agreed for your operation.

How do you test the connection between the shop, stock and invoicing?
TestWhat to doExpected result
VariantIn the shop, choose the blue cup and compare the reference and price in both systems.Code MC-AZ-01 identifies the blue cup in both. The white one retains its own code and price.
Paid orderConfirm payment for order MC-104, for one blue cup, in the test environment.One blue unit and two white units available. The team can link the order to the expected invoicing record.
Repeated confirmationReprocess confirmation of the same order MC-104 using the supplier’s test mechanism.One blue unit remains. The same sale has a single effect on stock, preparation and invoicing.
ReturnReceive and inspect the cup from MC-104. In this test it is intact and the team approves restocking.Two blue units after restocking. The movement, test refund and documentary adjustment are identified separately.
Missing referenceRepeat the test with a fictional variant without a matching entry in the management system.The team can locate the pending issue, correct the reference and resume the request once. No movement is assigned to the white variant.

Define when to reserve and release stock

Choose the source that determines the available quantity. If you sell in person and online, describe how quantities synchronise and how a failure is handled. State when stock is reserved, when the reservation expires and what happens if payment is declined or abandoned. This decision must match the platform’s behaviour and the preparation process.

In the fictional Mesa Clara shop example, a blue cup has reference MC-AZ-01 and two units available in the test environment. After an initial reservation, two sessions try to buy the last unit. The expected result is to prevent confirmation of a quantity that cannot be delivered, or follow an explicitly defined ordering policy. The test compares what the customer sees with the quantity and status recorded by the team.

Define when to reserve and release stock
StageDecision to documentTest evidence
Add to basketReservation or intention only?Quantity still available
Start paymentReservation deadline and identificationOrder status
Payment declinedRelease, or keep for how long?Consistent stock and message
CancellationRestocking and applicable conditionsDecision recorded and final quantity

Confirm payment through the correct source

Distinguish order created, payment pending, payment confirmed and dispatch. A thank-you page open in the browser is not sufficient proof of payment. Payment integrations should use the provider’s appropriate confirmation, handling repeated and delayed messages. Stripe’s fulfilment documentation illustrates why the customer returning to the site cannot be the only condition for preparing delivery.

Define who can change statuses and what evidence is recorded. An operator should not need to guess whether an order has already been prepared. In the Mesa Clara example, the test reference follows the catalogue, payment, email and preparation. If confirmation arrives twice, there is still only one dispatch task. Refunds and cancellations need their own statuses, without deleting the history needed to understand the order.

Illustrative order statuses
  1. Created

    Items and conditions are identified.

  2. Pending

    Awaiting the payment result.

  3. Confirmed

    The payment source confirms the expected status.

  4. Prepared

    The team carries out delivery only once.

Prepare commercial information and privacy choices

Gather the seller’s identity, contact details, product characteristics, costs, delivery, support and applicable cancellation and returns conditions. Consumer sales in the EU have specific information and fulfilment obligations; the official Your Europe guide helps identify that scope. The actual setup must be reviewed for the products, countries and customer type. A technical checklist does not establish legal compliance.

Inventory third-party resources before enabling them: analytics, advertising, video, maps or chat may load additional code and storage. Configure the relevant choices before those optional resources load, and test rejection, acceptance and withdrawal. The basket and essential payment flow need to remain understandable even when someone does not accept marketing resources. Also check behaviour on each page, rather than only when the shop opens.

Place a test order and follow every consequence

Use the provider’s test environment and products identified for testing. Work through variant selection, quantity, delivery, total, payment and confirmation. Then follow the team’s side: records, notifications, stock and preparation. Exercise a decline, an interruption before returning to the site, repeated confirmation and cancellation. Keep test results separate from real orders.

Common errors include calculating delivery charges only after the customer thinks they know the total, confirming payment before validating its status with the provider, and leaving the catalogue available with provisional data. Approval should retain test references and expected values. Before opening to the public, confirm the correct environment and credentials without making real demonstration charges. Whoever receives the first order needs to know the same sequence that was tested.

The worksheet connecting catalogue, team and implementation

Complete a worksheet for the main journey and add exceptions that change the operation. Include responsibilities and where evidence is kept. Review it when new product types, destinations or payment methods are introduced: a new option may change stock, displayed information and failure handling, even if checkout looks the same.

Worksheet for your project

Product type and initial catalogue:
Identifier, variants and required attributes:
Stock source and reservation rule:
Destinations, delivery and cost calculation:
Order statuses and who changes them:
Payment provider and confirmation source:
Repeated events, failures and cancellations:
Preparation, delivery and customer support:
Commercial information validated for the scope:
Optional resources and choice tests:
Test order references and results:
Shop name, invoicing software and connector version:
Variant in the shop / SKU / reference in the management system:
Source of prices and quantities / direction of updates:
Test order / balance before and after / associated document:
Repeated confirmation / number of movements, preparations and documents:
Return / inspection / restocking / refund / adjustment document:
Missing reference / alert / responsible person / result after correction:
Person responsible for approving launch:

Sources and criteria

Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.

Wellinton Oliveira

Written by

CEO of Lyntev

Technology with context, original analysis and sources you can consult.