Product matching
Matched product identifiers, sizes and variants across the three systems.
CLIENT CASE · API · INVENTORY · FBS
I connected Ozon and Wildberries products, orders and stock with MySklad inventory records. The project covers reservations, dispatch, cancellations and returns for seller-fulfilled orders.
01 / TASK AND SOLUTION
The integration needs to account for what happens to a product at each stage. I worked through the relationship between an order, its reservation, dispatch and return, including discrepancies between services.
Matched product identifiers, sizes and variants across the three systems.
Linked accepted orders with reservations so committed products are reflected in available stock.
Accounted for the order’s path to dispatch and the point at which its reservation is released.
Handled cancellations separately from returns. Returned stock becomes available after receipt and inspection.
Included status reconciliation and follow-up checks after API failures or delays.
Accounted for availability limits and reservation checks when only one unit remains.
02 / RESULT
The exchange accounts for products, reservations and order states. Stock changes are confirmed after checking the exchange result; temporary discrepancies require reconciliation.
Marketplace updates can arrive with a delay. Last-unit availability needs limits and follow-up checks; simultaneous orders cannot be ruled out entirely.
03 / PUBLIC MATERIALS
This page uses an illustration of the architecture. Store data, orders, access credentials and the client’s source code remain private.
I review how your products, orders and stock are connected, then propose an exchange that fits your workflow.
HAVE A PROJECT?
Send a link, screenshot or short description. We agree on scope, price and timeline before work starts.
Telegram ↗alexgtup@gmail.com