Build a product sheet before importing
Prepare a sheet with a stable product identifier, name, price, availability, images and the attributes customers use to choose. Record which system owns stock and prices. Decide how variants, unavailable products and substitutions appear; a colour and a size must identify the item that will actually be shipped.
Illustrative example: a shirt has three sizes. Check each size independently in the card, cart and order, rather than treating one successful purchase as proof for every variant.
Agree on the order and payment rules
Write down delivery areas, calculation rules, payment methods and the person who confirms an order. Have the business approve customer information about delivery, returns and contact options. Provider connection requirements and fees must be checked with the selected provider; a button labelled Pay does not prove payment is connected.
Use a provider-approved test mode where available. Test success, rejection and interruption. Refreshing a page must not silently create another order or change an unpaid order to paid.
Test the entire mobile journey
- Find a product through categories, select a variant and change quantity in the cart.
- Check delivery cost and the final total before confirming; try an invalid address or missing required field.
- Confirm what the customer sees and what the manager receives, including order number and payment status.
- Test cancellation, unavailable stock and a repeated submission; record expected outcomes.
Make products reachable without site search
Google recommends links from categories to products; its crawler generally does not submit searches in a search box. Check that useful product pages are reachable through ordinary navigation and have a consistent address.
For each published language, review product names, units, price presentation, checkout errors and confirmation messages. A translated menu with an untranslated checkout is an unfinished customer journey.
Official source: Google Search · Ecommerce navigation
Decide who runs the store tomorrow
Assign responsibility for stock changes, fulfilment, customer replies, renewals and recovery. Give the owner appropriate access and document how to edit one product and find one order. Confirm that backups can be restored, rather than merely checking that a backup file exists.
The launch record should contain the tested scenarios, unresolved issues, responsible people and the decision to open sales. Block launch for an incorrect total, lost order or ambiguous payment status; schedule cosmetic changes separately.
Discuss your project
Tell us your goal, languages and required functions. We will agree on the scope and next steps.