Skip to content

Usage

Orders > Conrad > Listings lists the mapped products with their state: not listed, waiting for the marketplace, live, withdrawing, or with an error. Add a product with its EAN (the barcode is the product reference and also the offer SKU), or add all products of a category. Stock and price switches decide what is pushed. Sync now queues the sync at once.

An offer is created with one offer import (OF01) and the marketplace processes it afterwards: the product shows Waiting until the import has finished. The import is recorded before it is sent, so a lost answer never leads to a second import; if Conrad did not confirm it within 30 minutes the products show “did not confirm” and are sent again. When the marketplace rejects a line (for example “The product does not exist” for an EAN that is not in its catalogue) the reason from the import’s error report is shown on the product. Fix the cause and press Retry.

The offer carries the product ID (EAN by default), your price including VAT, the stock, the condition “New” and your delivery time. Offers on products that do not exist in the Conrad catalogue are rejected: this version does not create catalogue products.

Removing a live product from the list (or deleting the product) does not just forget it: the row becomes Withdrawing from Conrad, the next sync sets the offer quantity to 0, and the row disappears when Conrad confirmed it. A withdrawn offer is never listed again by itself; map the product again to reuse the offer.

Map each CS-Cart category to a Conrad category (the category tree is loaded from your Conrad instance, H11). The mapping carries the price markup for its products. The Offer fields page shows the custom offer fields of your account (AF01), for example Conrad’s lead time, shipping class or warehouse, and lets you map CS-Cart product features to them; required fields are marked. Which fields are required is Conrad’s decision for your account. Price, stock and delivery rules are on Rules.

New orders wait for your answer at the marketplace. With Accept new orders automatically on, the next import run answers every line (OR21) and the answer is based on your stock:

  • a line is accepted when its offer is live and mapped, the product is active, and the units in stock (minus units already promised to other orders of the same run and to accepted orders that are not placed yet) cover the quantity;
  • every other line is refused (not enough units, an unknown, withdrawn or removed offer, a disabled product). Conrad cancels refused lines; nothing is oversold. The reason is written to the log without buyer data.

The accepted units stay reserved until the order is imported: the stock sent to Conrad and the acceptance of the next orders leave them out, so an order that waits for the buyer’s payment for days is never sold a second time. The Orders page shows such an order as Accepted, waiting for Conrad. A reservation ends when the order is imported, or when Conrad cancels or refuses it. Limits: a reservation is written only after the add-on accepted the order itself (OR21 with a confirmed answer). An order you accept by hand in the Conrad back office (automatic acceptance off), or an acceptance whose answer was lost (timeout), reserves nothing until the order is imported, so the next stock push may offer those units again; keep a stock buffer on the Rules page if you accept by hand.

The buyer’s address is only released after acceptance, so the order is imported in the same or a later run. With the option off, answer the order in the seller back office; it is imported afterwards. Orders that are not confirmed yet (waiting for payment) are imported once Conrad releases them for shipping.

Each imported order becomes one CS-Cart order (in Multi-Vendor owner mode the usual parent order with one order per vendor) with the accepted lines only, the buyer, the delivery and billing address (the three letter country code of Mirakl is converted to the two letter code), company and tax number in the order notes, and the prices as sold. Refused and cancelled lines are left out. An order whose accepted product is not mapped is not imported and shows the reason (“No product mapping for barcode …”); it is retried every hour.

An order is imported once: the import is recorded before the order is placed, and if a run stops between placing the order and recording it (a timeout, a slow mail server), or the add-on was reinstalled, the next run finds the CS-Cart order by the Conrad order number in its notes and adopts it instead of placing a second one (the log says “was placed before as order #…”). After an installation, orders that Conrad changed for the last time before the installation are not imported.

The imported order sends no e-mail to the buyer from your shop by default (Conrad owns the buyer contact, and the buyer address is a Conrad notification address); switch Send the shop e-mails to the buyer on the Rules page to change that. Your own and vendor notifications are not changed.

When the order is shipped, delivered, canceled or refused at the marketplace, the CS-Cart order status follows the mapping on the Rules page, forward only: an older Conrad state read again never moves the order back, an order in Complete, Declined, Failed or Canceled is never changed, and an order whose status you changed yourself keeps it (the log says why). In Multi-Vendor the vendors’ orders follow, the parent order stays as it is.

When every unit of a CS-Cart order is in a shipment (in Multi-Vendor owner mode: every unit of every vendor’s order) and a shipment has a tracking number, the add-on sends the carrier and the tracking number (OR23; a carrier of the marketplace’s carrier list is sent by code, any other by name and tracking link) and then validates the shipment (OR24), because OR24 confirms the whole order. A partly shipped order waits. A repeated step is not sent twice. The order is read first: tracking and validation go out only while Conrad shows it in shipping. An order Conrad cancelled or refused meanwhile is marked Closed at Conrad with the reason and is not tried again; an order still waiting for payment is tried again later. Orders that cannot be reported yet never hold up newer ones. Conrad asks for a tracking id and a tracking URL; put your carrier link with {tracking} on the Rules page.

Cannot supply on the Orders page cancels all lines of an order that has no shipment yet (OR33). The reason field can stay empty: the first cancellation reason of your marketplace (list RE01) is used. A shipped, closed or already cancelled order is refused here: refund it instead.

Refund on the Orders page sends a credit note for every shipped line of the order (OR28). The add-on reads the order first and copies, per line, the line price without shipping (price), the line’s shipping (shipping_price), their taxes and the order currency as Conrad returned them; a line that was already refunded is skipped, so a second click, a retry after a timeout or a second admin refunds nothing twice. A line that is refunded in part is refused with a message: finish it in the back office. The reason is the first refund reason of your marketplace (RE01) unless you type a code. A refund cannot be undone. Conrad’s seller help says prepaid orders can be refunded from “Shipping in progress”; this version refunds shipped lines only, earlier refunds are done in the back office.

Return requests of the marketplace appear on Returns with order lines and reasons. Approve accepts the return request (RT21). An accepted return is noted on the CS-Cart order; the order moves to the “returned” status of the Rules page (default: Canceled, which puts the goods back in stock) only when every unit of the order is returned. A return of part of the order changes nothing else. The status follow never changes an order in Complete, Declined, Failed or Canceled: with the default mapping a delivered order is already Complete, so a full return after delivery leaves it Complete. Put the returned goods back in stock by hand (or change the status yourself), and refund the lines with Refund. Refusing a return and checking the received goods are done in the seller back office.

Log shows every action with filters and a CSV export (the API key and buyer data are never stored). Jobs shows the queue, retries and the jobs that gave up, with a Retry button.