Turkish Marketplace Listings: SKUs, Barcodes, Photos and Brands

سفير تركيا · Sunday at 11:59 PM

A Consistent Catalog Makes Every Order Fulfillable

Organizing product data is essential before listing; general illustrative image.

The same item may appear in two marketplaces and an independent store, but customers need one clear promise: what product, which variant and how many pieces will arrive? This guide helps physical-product sellers in Türkiye build a unified record and adapt it to each channel's fields rather than maintain conflicting files.

Goal: traceable products, identifiers, images and stock from page to invoice and shipped item. Category and listing rules vary by channel; use current upload requirements.

Start with one product profile the team can trust

An organized catalog begins outside the platform dashboard. Create a master record for each product covering name, brand, supplier, material, dimensions, piece count, parcel weight and linked images. Assign approval ownership and record amendment dates and reasons. This keeps sales and fulfillment descriptions aligned and prevents scattered files competing as sources of truth.

Separate relatively stable information, such as material and model, from changing prices and quantities. Use statuses such as draft, document needed, ready to list and published. Missing information is not permission to assume it: 'cotton' and 'made in Türkiye' need appropriate evidence. Profiles also support objections and explain cross-platform differences.

Profile field	Illustrative example	How to verify
Product name	Fabric wardrobe organizer	Match sample and packaging
Variant	Blue, medium, one piece	Check color, dimensions and count
Identifiers	Internal SKU and original product identifier if available	Connect codes to sample and supplier
Material and dimensions	Fabric composition and dimensions in centimeters	Actual measurements and supplier documents
Safety and responsible entity	Category-applicable information and warnings	Product file and relevant rules
Stock and images	Actual quantity and images for each variant	Stock count and image review

Step output: an approved product record whose information sources your team can trace.

Separate SKU, GTIN and barcode graphics

SKU is an internal identifier chosen to connect goods, stock and orders. GTIN is a global product identifier under its system, while a barcode is a machine-readable representation that may carry it. A platform field called 'barcode' does not make any chosen number a valid global identifier; read field, channel and category requirements.

Request manufacturers' original identifiers and compare with packaging. Do not purchase unknown numbers or borrow those of similar goods. For own-brand products, assess identifier acquisition or channel-permitted exemption before producing labels. Internal identifiers do not establish brand authenticity, and global identifiers do not replace purchase-source evidence.

Keep SKU patterns short and stable, for example category, model, color and size, avoiding visually confusing characters. Map your code to every platform identifier and never reuse a discontinued item's code for different goods.

Give each variant its own identity and quantity

Color, size and pack quantity can change actual customer receipts. GTIN identity rules distinguish products and variants; do not give every size one number merely because the trading name is shared. WooCommerce variants can have separate prices, codes and stock. Marketplace grouping follows its rules, so do not transfer independent-store variant trees without matching them.

A hypothetical three colors and four sizes yield twelve possible combinations. Verify actual availability: images showing every color do not establish every size. Disable unsold combinations and connect correct color images. A two-piece pack is not the same offer as a single piece despite identical appearance.

Hypothetical variant	Physical quantity	Reserved	Available for sale
Blue, small	10	3	7
Blue, medium	8	2	6
Gray, small	6	1	5
Gray, medium	5	0	5
Total	29	6	23 units

Here, twenty-nine physical units minus six reserved units leave twenty-three available. Reservation is not shipment but temporarily prevents promises to other customers. Define when canceled or expired orders release reservations and test each channel's behavior.

Match existing products before creating pages

Platforms may let you add offers to existing product records rather than create another. Trendyol Academy describes catalog addition; the seller's priority is matching before linking offers. Review identifiers, model, size, count and contents rather than relying on thumbnails or similar brand names.

Wrong-page offers generate orders you cannot fulfill as expected. Distinguish new from refurbished, versions with and without accessories, bundles and single pieces. Record comparison outcomes and reasons for accepting a match. For differences, use product creation or correction routes instead of hiding them in offer descriptions.

On shared pages, distinguish data you control from platform-controlled information. Retain offer descriptions, supplied packaging images and documents. Recheck shared-page changes: an earlier match does not protect against later model or quantity changes.

Write comparison-friendly titles, categories and attributes

Begin with product type, brand or model and key feature, adding variants where required. Avoid repeated keyword lists or unsupported 'best' promises. Choose the category closest to the product because it determines fields, policies and requirements; an easier category used to evade mandatory fields may create larger problems.

Fill structured attributes rather than burying everything in long paragraphs. Material, size, dimensions, quantity and compatibility help filtering, comparison and correct choices. Distinguish product from shipping-parcel dimensions and body from garment measurements. Place units beside numbers and explain approximations and measurement methods where material.

For Türkiye, prepare accurate Turkish matching the product, with human review especially for materials and warnings. Additional Arabic descriptions should match rather than expand promises. Do not invent attributes to outperform competitors or allow machine translation to alter sizes or contents.

Samples, measurements and images must describe the same product; general illustrative image.

Use genuine images with clear rights

Photograph approved samples and verify supplied batches match. Include overall, material/detail and measurement or use images where helpful. Check current main-image, background and overlay rules; one channel's requirements are not universal.

For supplier photography, obtain use rights and verify the same version is shown. Purchasing goods does not automatically permit republishing every online image. Keep originals and permissions where needed, linking files to correct variants. Do not display extras as though included.

Tools may improve lighting or remove backgrounds without changing product reality. Review colors, edges and labels afterward, and do not use wholly generated images as evidence of unphotographed goods. General illustrations can explain store activity but do not replace images supporting purchase decisions.

Complete safety information before selling

Online publication does not remove safety information or responsible-party traceability. The Ministry of Trade publishes classification guidance to help entities and platforms identify product-advertisement fields under the relevant regulation. Assess category-specific manufacturer, importer or responsible-entity details, warnings and distinguishing product information as applicable.

Do not assume every product needs identical marks or certificates. Toys, appliances, cosmetics and clothing have different files, depending on product nature and presentation. Obtain information from suppliers and relevant sector authorities, distinguishing trademarks, conformity marks and test reports. A packaging logo alone is not a complete compliance assessment.

Record each document, date and covered products. Recheck applicability after supplier, model or material changes. Suspend unsupported safety or use claims, or the listing, until resolved. Completing a dashboard field does not establish the truth of its contents.

Link offers to fulfillable stock and prices

Catalog quality extends beyond approved descriptions to quantities you can ship and prices you can honor. Define authoritative stock sources, pricing authority and channel-update routes. Do not let employees edit separate unlogged files because a final update may silently overwrite correct information.

Maintain safety stock where synchronization is slow or offline sales occur, recording the reason and review method. Do not permit backorders against zero stock without suitable delivery promises, or assume supplier arrival makes every item ready before inspection and counting. Separate damaged, transferred and reserved stock from saleable quantities.

Review currencies, tax, shipping, discounts and offer dates by channel. Import-file amounts may be base prices while another platform expects final prices. Test one case and calculate customer totals before wider uploads. Do not generalize a training example's commission or tax rate to every category.

Upload a small batch and inspect import results

Use the current channel template or documented integration and verify field names, types and permitted values. Retain before-and-after files rather than uploading the entire database to test a new format. Start with simple, multivariant and extra-field products to reveal different errors early.

Listing stage	Action	Condition for proceeding
Before upload	Check samples, information and rights	Complete master profile
Trial file	Upload a small varied range	Correct fields and codes
Review	Inspect customer-facing pages	Matching image, variant and price
Connection	Test one variant's stock change	Other variants remain unchanged
Approval	Record file version and acceptance time	Rejection causes resolved
Expansion	Add remaining batch and review results	Accepted and rejected counts known

After upload, compare submitted, accepted, rejected and pending counts. Technical task acceptance does not publish every product. Open sample pages as customers see them and test colors, sizes, images, prices and shipping times. Retain errors and task or technical-request identifiers for tracing.

With integrations, check current-version limits and permissions and test updating one product without deleting other fields. Do not include access keys or customer data in public support messages. Fix source data, then retry affected parts; repeating unchanged uploads does not resolve rejection causes.

⁦⁩ Fix rejection causes instead of creating duplicates

Start with platform messages and classifications, linking them to master profiles. Causes may include missing fields, invalid values, brand documents, images or wrong matching. Do not create a new record for every rejection because that duplicates products and hides processing history.

Rejection or fault	What to inspect	Controlled correction
Identifier mismatches the product	Quantity, size, brand and package	Correct mapping or obtain the identifier from its source
Variant in the wrong group	Product attributes and color/size relationships	Rebuild grouping under channel rules
Missing required information	Category, safety fields and responsible entity	Complete documented information
Misleading or unauthorized image	Sample, rights and piece count	Permitted actual images and package clarification
Price or stock differences	Master file, integration and latest update	Correct the source, then test synchronization
Brand or specification claim	Invoice, permission and claim evidence	Remove unsupported claims or provide evidence

For brand-rights or safety objections, assemble correct documents and identify covered products. A concise account of the problem, correction and attachments is clearer than lengthy assertions of trustworthiness. Do not alter invoices or substitute supplier details to appear compliant; correct relationships and data at source.

Record owners, follow-up dates and decision status, then verify the correction appears on the page. If problems persist, pause affected offers until the route is clear. A smaller accurately fulfillable catalog is operationally better than a large range requiring daily searches for what was promised.

Catalog-to-fulfillment links prevent sending unwanted variants; general illustrative image.

⁦⁩ Monitor versions and changes after publication

Regularly review high-demand, high-return and supplier- or packaging-changed products. Keep approved data versions with clear dates or numbers and logs explaining who changed prices, images or dimensions and why. New staff should not rebuild knowledge from scattered messages.

Compare return reasons with page information. Repeated 'smaller than expected' complaints require reviewing measurements, explanations and images before blaming customers. Missing pieces require checking contents and sales-unit versus storage-unit mapping. Causes may lie in records, fulfillment or suppliers; image changes alone cannot correct differing warehouse goods.

When discontinuing products, preserve connections to earlier orders, invoices and returns rather than deleting identity everywhere. Arrange usable exports of data and images for channel migration while respecting terms. Organized master records reduce migration time and preserve operational history without incomprehensible copies.

⁦⁩ Specific questions and pre-expansion checklist

Should I use the same SKU on every platform?
A unified internal code is possible if formats are accepted, with mapping to each platform's identifier. Do not assume platform product identifiers equal your internal code or GTIN.

Does a supplier image prove authenticity?
No. Images describe offers, while purchase sources, rights and appropriate documents establish other matters. Check samples, invoices and required permissions by brand and channel.

Does listing approval complete safety and operations?
Approval is one step. You remain responsible for accurate information and documents, matching goods, stock and prices, and fulfillment and returns capability.

A complete master profile has known information sources.
Every variant links to correct identifiers, images and quantities.
Category, count, size and packaging match the sample.
Images, rights and safety details are reviewed.
Trial files are accepted and customer pages checked.
Amendment and rejection logs and follow-up owners exist.

Start with products passing review, then expand gradually. Catalog quality means clear purchases, easy fulfillment and delivered goods matching displayed promises rather than page counts alone.