Map the records
Identify where product names, prices, images and stock are maintained. Note which updates are automatic and which depend on someone copying information.
A customer should not discover that the website and shop describe the same product differently. We help Kingston upon Thames retailers organise product records, availability and store information around a maintainable source of truth.


Photo: Kreepin Deth
Kingston Market Square.jpg (Source) · CC BY 3.0
Reduced-resolution copy; cropped to fit the card. Available under the stated licence.
These are the questions we would work through for this Kingston upon Thames brief. The final scope depends on your current site and how the business operates.
Identify where product names, prices, images and stock are maintained. Note which updates are automatic and which depend on someone copying information.
Test a manageable selection that includes variants and unusual fulfilment rules. Resolve those cases before importing the full catalogue.
Check how an online sale reaches the team and changes availability. Define what happens if a connection fails or data arrives late.
Kingston upon Thames is the town and borough name; this page concerns the town as a service area. For a retailer with premises and an online store, product data often passes through several systems. We can map those relationships before recommending a new storefront. Prices, variants and stock need defined owners, especially where staff also take orders by phone or in person. A better-looking shop will not fix conflicting records on its own.
Send sample product records from the systems you use and explain how staff update them. Include a product with several sizes, colours or fulfilment options.
Compare the same item across the website, internal record and order confirmation. The customer-facing details should agree, with a clear owner for future corrections.
Compare the public product journey at Alif Meem Fragrances with the inventory responsibilities described in our RJ Health Solution portal case study. They are separate Xapner projects, not a combined Kingston system.
A Shopify or WooCommerce integration needs an agreed source of truth for product and stock data. Bring an example of a returned, reserved or unavailable item as well as a normal sale.
A few details worth settling before design or development begins.
Possibly, if the systems support a reliable integration. We need to inspect the available connection, ownership rules and recovery process before promising synchronisation.
Not automatically. Review discontinued items, duplicate records and missing information first. Keep useful URLs or redirects where products have an appropriate replacement.
Use the short form below, email or WhatsApp to describe the work. We review the brief remotely and agree deliverables, responsibilities and costs before starting. Any third-party subscriptions or ongoing support need to be included in that discussion.