Usage

First setup (once)

1. Categories: search the N11 category tree (names are Turkish and carry their path, searching ignores accents), pick a lowest-level category (N11 accepts products only there), choose the CS-Cart category it belongs to and, if you like, a markup and a brand name for it. A product uses the deepest mapped category on its path.
2. Attributes: for each mapped N11 category the attributes N11 marks as mandatory are listed (colour, material …). Map each to a CS-Cart product feature or give a fixed value. The brand is not listed: the brand name of the category mapping (or the default brand on the Rules page) is sent as the category’s “Marka” attribute. Feature values are matched with the allowed N11 values by name (accents and case ignored); free text is sent only where N11 allows it.
3. Rules: markup, price endings, stock buffer, default brand, VAT, delivery days (N11 “preparing days”), status mapping (see Configuration).

Listings

1. Add products: by product ID with a stock code (empty = a code made from the product), or Add all products of this category. Tick Already on N11 to link a product that exists there under the same stock code.
2. The sync creates products that are not on N11 yet (state “Not listed yet” > “Waiting for N11” > “Live on N11”). N11 answers asynchronously; the add-on reads the task result and shows the reason per product in the Last error column (for example a missing mandatory attribute or a title that is too short). Fix the data and press Retry. A new product may still wait for N11’s own approval after the task.
3. Stock and price of live products are sent when a product is saved and at least hourly. Sync now queues an immediate run. The result of each task is read back and a rejected item shows its message.
4. One CS-Cart product becomes one N11 product with one stock code. Product options are not sent as N11 variants. Changes of title, description or images after creation are not sent in this version; stock and price are.
5. The stock code is the key of every later call, so it must not change once a product is live.

Orders

• New N11 packages become CS-Cart orders once: buyer name and e-mail, the delivery and invoice address, company and tax number for commercial buyers, prices as sold (after the seller’s own discounts), and a note with the N11 order number.
• An order whose stock code is not mapped is not imported; the Orders tab shows the reason and the import is retried every hour.
• When a CS-Cart shipment exists for the order (and “Send picking” is on in the Rules), the add-on approves the lines of the package at N11 (status Picking). N11 then arranges the cargo: the cargo company and the tracking number are read back with the package. A seller cannot report an own tracking number through the N11 API, so the “own carrier” option of the shared Rules page has no effect for N11.
• Later changes on N11 (shipped, delivered, cancelled) follow into CS-Cart through the status mapping.
• Cancel at channel on the Orders tab cancels the lines of an approved package (partial cancellation); leave the reason empty to use N11’s stock reason, or enter a reason ID from the N11 list.

Returns

The Returns tab lists N11 return requests with the product, reason and status, linked to the CS-Cart order (a note is added to the order). Approve accepts the return. Denying or postponing a return is done in the N11 seller panel.

Jobs, log and connection

• Jobs: counts per state, the list with the last error, Retry, Remove and Run the queue now.
• Log: filter and export what happened and when, per stock code and order.
• Connection: API key, API secret, integrator name, shipment template, Test connection. N11 has no test environment: both modes use the real API, and Test connection only reads.