Publishing and keeping a catalogue up to date on a marketplace
An e-commerce seller trading on a general Turkish marketplace was managing listings by hand, with a risk of error on every update.
The context
The marketplace in question exposed an API for publishing products, managing stock and receiving orders, but using it directly in production carried a real risk: a category-mapping error, a miscalculated price or an incorrect stock figure could immediately turn into a listing published with wrong data, visible to thousands of buyers. The seller needed a management tool able to prepare and check publications before anything was actually sent.
The goal was to build a robust integration, with built-in safety so a configuration mistake couldn't go straight to production unchecked.
What I did
-
Marketplace API integration
Building the exchanges for publishing products, updating stock and prices, and receiving orders from the marketplace.
-
Simulation mode by default
Every new configuration or change to a publishing rule first goes through a simulation mode, which shows what would be sent without actually sending it.
-
Validation before going live
Automatic checks on required fields, category mapping and price consistency before switching to sending anything for real to the marketplace.
-
Tracking received orders
Automatically feeding orders placed on the marketplace through to the seller's management system, for centralised rather than scattered processing.
Frequently asked questions
Why a simulation mode rather than a simple test environment?
Does simulation mode slow down routine updates?
Does this approach apply to other marketplaces?
How are orders received on the marketplace handled?
Describe your need in one minute
A few targeted questions so I can reply with an estimate rather than another questionnaire.