Amazon Turkey Integration: ASINs, FBA/FBM and Order Flow
How Amazon Turkey integration works: ASIN matching, pending-order logic, FBA versus FBM stock, report-based data flow and settlement tracking from one panel.
An Amazon Turkey integration connects the listing, order, shipping, return and settlement work in Amazon Seller Central to your own e-commerce platform and ERP over Amazon's selling API. An order is written to the ERP when it is ready to ship, a stock change updates the Amazon listing, and settlement reports are matched against orders. Amazon's Turkish marketplace runs on the same logic as Amazon everywhere else: the product identity is the ASIN, data moves through reports and batch feeds, and an order is not released to you until payment verification clears. If you already sell on Amazon in the US or EU, most of what you know carries over; this guide covers the rules and how an integration follows them.
The ASIN: Amazon's product identity
Every product on Amazon has an ASIN, and that number belongs to the product, not to the seller. If you sell an item already in the catalogue, you do not create a new product; you find the ASIN by barcode and attach your offer to it. If you sell your own brand, you create the product, Amazon assigns a new ASIN, and the detail page is shaped by your content.
The integration handles the two cases as separate flows. Adding an offer to an existing ASIN is fast; it needs only a seller SKU, price, quantity and condition. Creating a new product asks for category-specific mandatory fields, brand data and image rules; after the feed is processed an error report comes back listing every missing field. A GTIN-type barcode is usually required as the product ID; if you have none, brand registry or an exemption are the usual routes — check current conditions in Seller Central.
The mapping rule is the same as elsewhere: bind your own SKU, the Amazon seller SKU and the ASIN as a one-to-one triple. For variation products the parent-child relationship is built separately; size and colour variations get their own ASINs but share one page. The practical steps are in matching products by SKU and barcode.
Order statuses: pending, unshipped, shipped
The most confusing part of an Amazon order is the "pending" state. When a customer places an order, Amazon first verifies payment; during that window the order appears in your list but the address and line details are withheld. Once verification clears, the order becomes "unshipped" and can be dispatched. On dispatch it becomes "shipped", on delivery "delivered". Cancellations and returns are tracked as their own states. In practice the flow runs like this:
- The order lands as "pending". The integration sees it and reserves stock but does not yet write it to the ERP.
- When the order becomes "unshipped", customer, line items, shipping preference and payment details are written to the ERP.
- The warehouse picks; the shipping label comes either from Amazon's buy-shipping service or from your own contracted carrier.
- Tracking number and carrier are confirmed to Amazon; the order becomes "shipped".
- The invoice is issued in the ERP and delivered to the customer; Amazon's invoice-upload rules vary by category and seller type.
- Delivery moves the order into the settlement period.
Reserving stock on a pending order without booking it in accounting is an Amazon-specific balance. Skip the reservation and you sell the unit elsewhere; book it and cancelled pending orders litter your ledger.
Late shipment and cancellation rates feed Amazon's account health metrics. When those cross certain thresholds, selling privileges can be restricted; the exact conditions are in Amazon's current seller policies. Managing every channel's orders in one list keeps those rates under control — see multi-channel order management.
FBA and FBM: two different stock worlds
There are two ways to fulfil on Amazon. With FBM (merchant fulfilled) the unit leaves your own warehouse; stock, shipping and returns are yours. With FBA (Fulfilment by Amazon) you send inventory to an Amazon facility in advance; when an order arrives, Amazon packs, ships and handles the return. The same item can be listed as both FBA and FBM.
For the integration, FBA is a separate stock source. Amazon warehouse stock is read from reports and never mixed with your own. Which figure you expose to other channels is your choice: only your own warehouse, or the combined total? Bulutegra keeps that distinction per warehouse inside a single stock pool; as FBA stock runs down the FBM offer can take over, or the reverse, depending on how you configure it. Inbound shipment plans, receiving discrepancies and lost-inventory reimbursement are covered in Amazon global FBA and FBM integration.
Report-based data flow and stock-price sync
Amazon's selling API does most of its work asynchronously: a stock or price update is submitted as a feed, Amazon returns a processing ID, and the result is polled later. Order, inventory and settlement data likewise arrive mostly through reports that are requested, generated and downloaded. Sellers used to instant single calls find the model slow, but at high volume it is more reliable.
The integration's job is to make that asynchronous flow invisible to you. Bulutegra's system health screen shows the status of every Amazon submission; rejected rows are listed with their reason. Channel monitoring runs continuously; if orders or reports stop arriving from Amazon for too long, an alert fires. On pricing, the Buy Box is Amazon's own invention: among offers on the same ASIN, one wins based on price, delivery time and seller performance. The price matrix shows your Amazon Turkey list, sale and floor price next to every other channel; the profitability page calculates Amazon's contribution per channel after VAT, commission and return risk. Repricing logic is covered in price sync, repricing and BuyBox.
Customer messages, returns and settlements
Amazon limits direct contact with the customer; messaging runs through Amazon's own channel and is restricted to certain topics. Response time is measured. Seeing those messages in the same inbox as other marketplace questions and WhatsApp shortens reply times.
On returns, Amazon leans toward the customer: in certain categories a return request is approved automatically and a return label is issued; the item comes back to you, you inspect it and, where justified, apply a partial refund or open a dispute. FBA returns are received at the Amazon warehouse and graded as sellable or unsellable. The integration has to read those return outcomes from reports and reflect them in stock.
Settlements are periodic; each statement carries sales, referral fees, FBA fees, return deductions and any advertising charges as separate lines. Amazon may hold a reserve on the account under conditions set by your agreement. Bulutegra's payout and reconciliation tracking matches these lines to orders; anything unmatched is tracked as a missing payout, a return without commission credit or a negative-net order, with status, ticket and note fields.
How it works with Bulutegra
Bulutegra connects to Amazon Turkey over Amazon's selling API, and the same connection model applies to Amazon's other marketplaces. Setup follows four steps: Connect (seller authorisation, listings read; half a day), Match (SKU, seller SKU and ASIN bound one-to-one; one to three days), Watch (shadow mode for one to two weeks, read-only, so pending-order behaviour and the report cycle are seen alongside your current routine), and Hand over (write access for stock, price and shipment confirmation). The software was first used in the founding company's own multi-channel retail operation, Amazon included.
After handover, Amazon orders are written automatically to Nebim V3, Logo, Mikro or SAP; invoicing and shipping continue in your own routine. Once Amazon Turkey is running, expanding to Amazon's international marketplaces from the same panel starts with the cross-border marketplace integration guide; every channel is listed in the channels section.
To connect your Amazon Turkey store to your own systems, request a demo and our team will plan the setup around your FBA and FBM mix.
Frequently asked questions
Why can't I see the address on a "pending" Amazon order?
Amazon holds an order in "pending" until payment verification is complete and does not share the customer address at that stage. Once the order moves to "unshipped", the address and line items become visible. The integration lists pending orders but writes them to the ERP only when they are ready to ship, so cancelled pending orders never pollute your accounts.
Can I list on Amazon Turkey without my own barcode?
Amazon generally requires a GTIN-type barcode as the product identifier. If you sell your own brand without barcodes, routes such as brand registry or a GTIN exemption exist; conditions change, so check the current rules in Seller Central help. For items already in the catalogue, attaching your offer to the existing ASIN is enough.
How does stock sync work when I use FBA?
With FBA the unit ships from an Amazon warehouse and that stock is managed by Amazon. The integration reads FBA stock from reports, keeps it separate from your own warehouse stock, and pushes whichever figure you have chosen to your other channels. For FBM products, stock syncs directly from your own warehouse.
