1,513 Amazon and Miravia orders in four months inside PrestaShop

The starting point

Sports Equipment Store sells footwear and sports equipment from Palma del Río and keeps its own catalogue in PrestaShop. Opening Amazon and Miravia as additional channels extends its reach: products appear where other people already search, compare and buy. It also creates an operational problem. If every channel behaves as a separate shop, the same product, size and order have to be updated several times in different places.

That fragmentation is particularly delicate in a footwear catalogue. Each model multiplies into size variants, every variant depends on a correct EAN, and a unit sold in one channel must stop being available elsewhere before the same last unit is sold twice.

What we did

We developed a dedicated module inside the client’s PrestaShop to connect the store to the Amazon and Miravia APIs. PrestaShop remains the centre of operations; the marketplaces are connected channels rather than two parallel systems that need manual maintenance.

• Catalogue. The module publishes new products, preserves variant mappings and explains why a reference has not reached Amazon. In the capture, for example, invalid EANs are separated from marketplace rejections so each issue has a specific action.
• Stock. PrestaShop inventory is synchronised with the marketplaces and can reserve a safety buffer. The panel can force a resynchronisation and compare the sent figure with actual stock, reducing the risk of selling the same last unit through two channels.
• Orders. Amazon and Miravia sales are imported as PrestaShop orders with channel-specific states —pending, unshipped, ready to ship or cancelled—. The team works in its familiar workflow and can retry a failed import without rebuilding an order by hand.
• Diagnostics. A dashboard summarises active variants, stock discrepancies, unpublished products, size problems and references without incidents. The API log leaves a trace when an exchange with a marketplace needs investigation.

What selling on marketplaces adds

Amazon and Miravia expose the catalogue to demand beyond the traffic Sports Equipment Store attracts to its own store. That visibility can reach buyers who did not already know the retailer, test the catalogue across more than one channel and reduce dependence on a single source of orders.

The technical benefit is not merely being listed; it is doing so without duplicating the operation. One central catalogue, synchronised stock and orders collected in PrestaShop remove much of the manual copying, speed up fulfilment and give the team a shared view of what has sold.

There are costs worth stating plainly: marketplaces charge fees, impose their catalogue and service rules, and may reject a reference because an EAN or size is incorrect. The module does not remove that dependency; it makes its rules and incidents visible so the team can operate them deliberately.

The outcome

Between 1 April and 31 July 2026 —122 days—, the module brought 1,513 orders into Sports Equipment Store’s PrestaShop: 1,370 from Amazon and 143 from Miravia. All order amounts and identifiers are concealed in the published evidence.

That is an average of 11.23 Amazon orders per day and 1.17 Miravia orders per day. The combined average for the period was 12.40 orders per day. These are ordinary averages: they do not imply an identical volume every day, but keep the accumulated result meaningful when the case is read months or years later.

At the same point, stock control covered 1,023 active variants and showed zero differences between actual and synchronised stock. It did not hide what remained to be resolved: 31 variants not yet published on Amazon and 22 references with a size or EAN mismatch. That is the value of an operational integration: not a promise that platforms never fail, but a precise view of where each reference is failing and a route to correct it.