Order flow: how orders reach your ERP

How it works

1. Bulutegra reads your connected channels continuously. New orders land in the Orders (Siparişler) list without delay.
2. On channels where order transfer is switched on, each order is written into your ERP with the customer, line items, carrier and payment details.
3. Invoicing and dispatch carry on in your own routine. Status changes on the channel show up in the list too.

The Orders list shows every channel in one table, newest first. Search covers order number, document number, customer name and SKU; searching clears the date and status filters.

Statuses

The Status (Durum) filter offers: Awaiting shipment (Kargo bekleyen), Shipped (Kargoda), Delivered (Teslim edildi), Return / cancellation (İade / iptal), Not updated for 3 days (3 gündür güncellenmeyen) and Other (Diğer).

The ERP filter (shown with your ERP's name) tells you where the order stands on the ERP side:

• Pending in ERP: written to the ERP, not dispatched yet.
• Processed (dispatch / invoice): moved on to dispatch or invoicing in the ERP.
• Not transferred: no counterpart in the ERP.
• Different (channel ≠ ERP): quantity, amount or warehouse differs between the two sides.

If an order didn't reach your ERP

1. Find the order. Search the Orders list by order number. If it's missing, it couldn't be read from the channel: check whether that channel's card under Settings → API Credentials (Ayarlar → API Kimlikleri) says "credentials rejected".
2. Open the Not transferred view. The Not transferred (Aktarılmamış) chip on the Orders page lists orders that are awaiting shipment on the channel but don't appear in the ERP and have no transfer record. The Transfer column shows the error reason, if there is one.
3. Transfer it manually. The Transfer to ERP button on the row (labelled with your ERP's name) first shows a preview; once you confirm, the order is written.
4. Check the Transfer view. The Transfer (Aktarım) chip shows a transfer card per channel: running, ERROR, STOPPED or not connected. The Recent transfers table shows the reason for a failed row and a retry transfer (tekrar aktar) button.
5. Check Operations. Transfers you start by hand go through preview and approval on the Operations (İşlemler) page. If an operation is waiting for approval, nothing is written until you approve it.
6. Check your notifications. You get a notification for any order that couldn't be written to the ERP, and on your phone too if phone notifications are on. The account owner can see the answer to "why wasn't it transferred?" in the Events — with reasons (Olaylar — sebebiyle) table under Notifications → Alerts (Bildirimler → Uyarılar).

An order that couldn't be written isn't lost: it waits with its reason and is retried once the problem is fixed.

Common causes

• A code that isn't defined in the ERP. The channel codes and carrier mapping on Channels → Order Transfer (Kanallar → Sipariş Aktarımı) must exist in your ERP. Create any new code in your ERP first; the ERP rejects an order that arrives with an undefined code.
• An unmatched product. If an order line doesn't match a variant in your catalog, the order can't be written. See the Product matching article.
• Transfer is off for the channel. If the channel hasn't been handed over yet, its orders are only watched.

Bulk transfer

Select orders in the list and use Transfer selected to ERP. Only tick "write again even if already written" when you're sure: if you do, a second order is created in the ERP.

You can also ask the Assistant (Asistan): "has order … reached the ERP?"