Modanisa, Flo and İdefix Integration: Fashion, Shoes, Books
Integrating Modanisa, Flo and İdefix: size-colour variants, shoe-size stock, ISBN catalogue matching and a shared order flow connected to your ERP from one panel.
Integrating Modanisa, Flo and İdefix connects the product, order, shipping, return and payout work on these three vertical marketplaces to one panel — and from there to your ERP — over each one's seller API. Unlike the general marketplaces, each focuses on a product group: Modanisa on modest fashion, Flo on footwear and sportswear, İdefix on books, music, games and cultural goods. That focus has shaped each one's product card and variant structure around its category, and an integration has to follow suit. For an international brand, these three are often the most natural entry points into Turkey, because a vertical marketplace already speaks your product's language. This guide takes each in turn, then covers the shared order flow and the setup.
Modanisa: size-colour variants and an international customer base
Modanisa is a fashion marketplace and its product card is built accordingly. A product is listed under a model code with colour and size variants; each variant has its own barcode and stock. Category attributes are fashion-specific: fabric, pattern, sleeve length, closure type and season may be required. Image rules are strict too; whether the image must be on a model or flat, background and dimension rules vary by category. A product submitted with missing attributes waits in approval.
Modanisa's second distinguishing feature is the geography of its customers. The marketplace sells to many countries, and a share of orders carry a foreign delivery address. For those orders, shipping and paperwork follow Modanisa's model; the seller typically sends the item to a point Modanisa designates and the marketplace handles the rest. The integration separates domestic and international orders, writes that distinction to the ERP, and flags whether size conversion and multilingual content are needed. How size conversion works is explained in international size and measurement conversion.
Return rates in fashion are high and the main reason is size. Bulutegra's Size Finder module suggests a size from height and weight; Content Studio generates a size-chart image. Together they aim to cut "wrong size" returns — details in reducing return rates with Size Finder.
Flo: shoe-size stock and retail-chain logic
Flo's marketplace focuses on footwear and sportswear, and its product card is built for that. In footwear the variant is size, but unlike apparel sizing it uses a numeric shoe-size system, with women's, men's and children's ranges on separate scales. Each size has its own barcode and stock; when one size sells out, only that size is withdrawn and the model stays listed.
For the integration this means many variants and stock movement tracked per size. The way your own SKU holds the size (as a separate field or embedded in the code) has to map one-to-one onto the structure Flo expects. A size-conversion error means a 38 sold as a 39, which comes back as a return and a complaint. The matching step on Flo is therefore run with particular care; the method is in matching products by SKU and barcode.
Flo is also the marketplace of a retailer with a physical store chain. Campaign logic runs parallel to the store calendar: season changes, sale periods and special days are mirrored on the marketplace, and sellers are expected to take part. Running the campaign price through the calculator — commission, VAT and return risk — protects the narrow margin typical of sports footwear. The order flow is familiar: the order lands, the seller packages it, it ships with a contracted carrier and closes on delivery; shipping terms depend on the seller agreement.
İdefix: a shared catalogue keyed on ISBN
İdefix is a cultural marketplace selling books, music, film, games and hobby products, and its product-card logic is entirely different from the other two. For books the product identity is the ISBN, which is universal; everyone selling the same book attaches to the same card. Most books already exist in the İdefix catalogue. As a seller you create no card; you attach by ISBN and send only price and stock. That removes most of the product-upload work.
Creating a card is needed for items not in the catalogue: local publications, imported games, stationery and hobby products. These go through İdefix category approval and require book-specific attributes such as publisher, author, page count and language, or platform and age rating for games. Variants barely exist for books (hardcover versus paperback, say) but appear as colour and platform for games and hobby items.
Because many sellers offer the same book, competition on İdefix comes down to price and delivery time. The price matrix helps here: your İdefix price sits next to every other channel as list, sale and floor, and stops you dropping below the floor on fixed-price items like books. Campaign logic follows the cultural calendar: book fairs, back-to-school and New Year drive demand. In the order flow the order lands, the seller packages it, the label is generated and delivery closes it. Book returns are rare, but damaged-delivery returns do occur; barcode receiving in the warehouse applies here too.
Shared order flow and a checklist for vertical channels
All three marketplaces sit in the same list as your other channels in one panel. Before starting the setup, we suggest running through this checklist:
- Define your variant structure: colour and size for Modanisa, colour and shoe size for Flo, mostly no variants for İdefix. Can your own SKU carry that structure?
- Settle the product identity: barcode for Modanisa and Flo, ISBN or barcode for İdefix. Complete any missing barcodes first.
- Fill category attributes in your master catalogue; a missing field stalls approval when the product reaches the marketplace.
- On the channel with international orders (Modanisa), flag the need for size conversion and multilingual content.
- Draw up the campaign calendar separately for the three channels; plan stock and price around it.
- Take payout periods and commission models from the agreements; configure the reconciliation screen accordingly.
A vertical marketplace's strength is knowing what its customer is looking for. The Modanisa shopper checks fabric and closure type, the Flo shopper checks size and sole type, the İdefix shopper checks publisher and edition year. A product that leaves those fields empty may sell on a general marketplace but stays invisible on a vertical one.
Orders are written to the ERP with customer, lines, carrier and payment details; stock is managed from a single pool, so a size sold on one channel is deducted from the others. Customer questions from all three channels are gathered in one CRM inbox. Payout lines are matched to orders per channel; missing payouts and returns without commission credit are tracked on the same screen. The general framework is in what is marketplace integration.
How it works with Bulutegra
Bulutegra connects to Modanisa, Flo and İdefix over each one's seller API; all three sit in one panel alongside more than thirty-eight other channels. Setup follows four steps: Connect (seller details entered, products and variants read; half a day), Match (barcode, ISBN and variant structure bound one-to-one to your SKU, with size and shoe-size conversion verified here; one to three days), Watch (shadow mode: the system only reads for one to two weeks while you compare orders and variant-level stock movements with your current routine), and Hand over (write access enabled channel by channel). The founding company's own retail operation was fashion-heavy; syncing size and shoe-size variants was solved there first.
After handover, orders from all three channels are written automatically to Nebim V3, Logo, Mikro or SAP; invoicing and shipping continue in your own routine. Content Studio produces multilingual descriptions and size-chart images for fashion items; the quality tab fixes missing colour, size and category findings with one click. Why we chose this approach is explained on the Why Bulutegra? page.
To connect your Modanisa, Flo or İdefix store to your own systems, request a demo and we will build the setup plan around your variant structure.
Frequently asked questions
What changes when an international customer orders on Modanisa?
Modanisa sells to many countries and an order can carry a foreign delivery address. Shipping, paperwork and currency then follow Modanisa's model; the seller usually sends the item to a point Modanisa designates. The integration separates domestic and international orders; check your Modanisa seller agreement for current rules.
How do I manage shoe-size variants on Flo?
On Flo, footwear is listed under model and colour with size variants; each size has its own barcode and stock. The integration carries the size as a variant, syncs each size's stock separately and withdraws only that size when it sells out. Mapping the size system correctly is the most important step of the setup.
Do I need to create a product card for a book on İdefix?
Most books already exist in the İdefix catalogue under their ISBN. In that case you create no card; you attach to the existing one by ISBN and send only price and stock. Creating a card is needed only for items not in the catalogue (local publications, games, hobby products) and goes through İdefix category approval.
