Order transfer settings: which codes are orders written to your ERP with?

What is this screen for?

Kanallar → Sipariş Aktarımı (Channels → Order transfer) brings together every setting that decides how orders are written to your ERP. The transfer reads only these settings. A change you save takes effect on the next transfer run.

The screen has four sections: ERP connection, document constants, per-channel codes and carrier mapping. Section headings show your ERP's name.

This screen opens only for the account owner. The settings are not shown on a demo account.

Before you start: what must exist in your ERP

Your ERP rejects an order that arrives with a code it doesn't know. So first create these in your ERP:

• The integration service and a user to connect to it (user group, user name, password).
• The office, store and warehouse codes orders will be opened under, and a POS terminal.
• A credit card type code for each channel.
• A carrier code for each carrier you use.

The order is the same when you add a new channel or carrier: create the code in the ERP first, then enter it here.

1. ERP connection

1. Fill in Servis adresi (Service address), Sunucu adı (Server name), Veritabanı (Database), Kullanıcı grubu (User group), Kullanıcı (User) and Parola (Password). If a password is saved, the field is marked "kayıtlı" (saved). Leave it empty if you aren't changing it; the saved password is kept.
2. Press Bağlantıyı sına (Test connection). If it works you'll see "✓ bağlandı" (connected) plus the company, office and store details returned by the ERP. If it fails, you'll see "✗" and an error message. The test doesn't just connect, it also reads the user's details, so a wrong password is caught.
3. Press Kaydet (Save).

2. Document constants

These values are the same on every order: Ofis kodu (Office code), Mağaza kodu (Store code), Depo kodu (Warehouse code), POS terminal, Ödeme tipi kodu (Payment type code), Ödeme tipi açıklaması (Payment type description), Ödeme türü (Payment kind), Taksit sayısı (Number of instalments), Para birimi (Currency), Sevk yöntemi (Shipping method), Perakende sipariş ModelType (Retail order ModelType) and the micro-export fields (Mikro ihracat ModelType, Mikro ihracat Incoterm, Mikro ihracat ödeme yöntemi — micro-export payment method).

The accepted values are written next to each field name; for example, in the payment type code, 1 means credit card and 2 means EFT. Make your changes and press that section's Kaydet (Save) button. If you type text into a field that must be a number, a "sayı olmalı" (must be a number) warning appears.

3. Per-channel codes

Each channel is one row in the table:

• If the Paketle ne yapar (What Pack does) column says "kanca yok — paketle etkisiz" (no hook — Pack has no effect), the mark does nothing on that channel; you process the order in the marketplace's own panel. On some channels this step runs before the ERP write; the column says so.
• While a channel is Aktif (Active), Kredi kartı tipi, Etiket, Kargo kodu and SalesURL can't be empty. On micro-export channels, Kredi kartı tipi and SalesURL are enough. If a required field is empty, saving stops with an error that names the empty field.
• A marketplace you have just connected appears in the table by itself with an ayarsız (not configured) badge. Enter its codes and save, and it is linked to the transfer.
• For a channel that isn't in the list, type its channel code into the box at the bottom and press Kanal satırı ekle (Add channel row).
• You can remove a row with ✕; it is deleted when you save.

To save, press Kanalları kaydet (Save channels). If you removed any rows, the panel first warns that those channels' orders will no longer be written to the ERP and asks you to confirm. It then reminds you that a wrong credit card type or carrier code will make the ERP reject the order, and asks for a second confirmation.

The Aktif (Active) and Paketle (Pack) boxes are the same settings as the sipariş → ERP switch and the Picking/paketle box on the Kanal Anahtarları (Channel switches) screen.

4. Carrier mapping

This table translates the carrier name the marketplace sends with the order into your ERP's carrier code. Names are matched after removing every non-letter character and converting to upper case: "Aras Kargo" becomes ARASKARGO. You can add separate rows for different spellings of the same carrier. For a carrier with no row in the table, the channel's Kargo kodu (Carrier code) is used.

1. Press Satır ekle (Add row).
2. Type the carrier name on the left and the ERP carrier code on the right.
3. Press Kargo eşlemesini kaydet (Save carrier mapping). A row with either field empty is not saved.

Every save is recorded under the name of the user who made it.

If something goes wrong

• The screen won't open and shows a permission warning: this screen opens only for the account owner.
• The connection test shows "✗": check the service address and user details with your ERP administrator; don't change the connection details until the test succeeds.
• Saving fails with "boş olamaz" (can't be empty): one of the required codes of an active channel is empty. Fill it in, or untick Aktif (Active).
• An order wasn't written to the ERP: check that Aktif (Active) is ticked for the channel and that the codes exist in the ERP. For details, see the Order flow article.
• The carrier on an order is wrong: the carrier table on Kanallar → Eşleştirmeler (Channels → Mappings) shows the pairs seen on real orders. Compare and fix it on this screen.

Related articles: see Marketplaces and channel switches and Product code matching.