↑↓ selectEnter openEsc close

    1. Elbuz
    2. Kazakhstan marketplaces

    How to import orders from Forte Market: installments, credit and built-in statuses

    11 min readUpdated

    Elbuz picks up orders from your Forte Market seller account by API key and adds them to the order list shared with other channels — no manual re-entry.

    When you need this:

    • You sell on Forte and elsewhere — Forte orders become “Customer order” documents alongside the rest.
    • Buyers pay in installments or on credit — the document gets the “Installment” or “Credit” payment type.
    • A manager handles orders in Elbuz — their status changes only after a new change on Forte.
    • Forte statuses must match yours — the mapping is built in.

    Where to start: get a token in your Forte account and create an “API — market.forte.kz” template.

    What the Forte connection does

    • Order import — buyer, address, total and line items go into a “Customer order” document. The catalog is not imported from Forte: products arrive only as order lines.
    • Cards for unknown products — an item that isn't in your catalog isn't lost; it becomes a card in a service category.
    • Installments and credit — bank payment methods are recognized automatically and get their own payment types.
    • Built-in status mapping — Forte statuses are translated into yours without any tables.
    • Automatic import — every 5 minutes, only new orders, with no duplicates.

    What you need from Forte Market

    Forte needs just one value — the Token. This is the API key issued in your Forte Market seller account; it's sent with every request and confirms that the request comes from your store.

    Seller help: Working with the Forte Market API. The key is issued in the seller account; if there's no button, ask your marketplace manager — access isn't opened automatically for every account type.

    Anyone who gets hold of the key can read your orders along with buyers' contact details. Give it only to the technical specialist setting up the integration, and don't send it in open chats.

    How to connect

    1. Create an “API — market.forte.kz” template. Want to check first? Switch the “Active” badge to “Disabled”.
    2. Paste the token into the “Token” field of the “Connection” card. The form saves itself — there's no save button: in an active template Elbuz usually starts picking up orders on its own within 5 minutes, up to a thousand most recent. Don't want to wait? Click “Import”: the log shows right away whether the marketplace accepted the key (what's in the log).
    3. Open a few imported orders and compare line items, totals, buyer and status with your Forte account.
    4. Look at the line items. If products arrived as new cards in the service category, the SKUs on the marketplace and in your catalog don't match — fix this while there are still few such cards (how).

    You don't need to set a schedule: new orders arrive on their own every 5 minutes (automatic import).

    What comes with an order

    Forte dataDocument field in Elbuz
    order IDExternal number (used to recognize the order on later runs)
    recipient nameName
    recipient emailE-mail
    mobile phonePhone
    delivery city and addressCity, delivery address
    order totalDocument total
    payment methodPayment type (installments and credit)
    order statusDocument status (status table)
    creation and modification datesOrder date, modification date on the marketplace
    line items: name, SKU, price, quantityDocument lines

    In the document list, Forte orders show up in the “Source: name” column — it holds the template name. The order number on the marketplace is in the “Document number (site)” column.

    Stock and reservation

    An imported order lands in the “Orders” window as an unposted “Customer order” document. The run itself doesn't change stock: no reservation, no write-off. The only thing it updates on product cards is the “Number of sales” field: it's recalculated across all customer orders after each run where the marketplace returned at least one order.

    What happens next depends on what you do with the order:

    • If you post the order, it reserves the product — provided stock tracking is turned on in the “Working scheme” and there is at least one active warehouse. The reservation is released when the order moves to a final status (such as “Canceled” or “Returned”), or as sales invoices created from this order are posted.
    • Stock is physically written off by a separate sales invoice, not by the order itself.
    • An order that stays unposted doesn't hold any stock.

    A cancellation on the Forte side after import reaches Elbuz while the order is among the thousand most recent: the document gets a canceled status, and a posted order's reservation is released (how). More on posting and reservation — in the article about customer orders.

    Where products missing from the catalog go

    Forte doesn't send a product category. So an item is first looked up among your products — by the Forte product number among cards this connection has already created, then by SKU plus name, then by name alone. If nothing is found, a card is created for it in the source's service category.

    Such a card contains only the name, SKU, price and quantity — no description, photos or attributes. The general order of item matching is described in the overview of order import via API.

    The service category is created at the tree root; its name starts with the word “Products” and ends with your template name. It's created disabled, with the export flag cleared. If a category with that name already exists at the root, later runs put new cards into it instead of creating a second one.

    Every card this connection creates remembers its template and Forte product number. You can find all such cards in the service category of the catalog tree or by filtering the product list on the “Source: name” column. The next order with the same Forte product finds this card by the saved number and doesn't create a new one.

    You can move the cards into your own tree. Order lines refer to the card itself, not the category, and later orders find the card by its Forte product number wherever it sits. After that you can delete the empty service category; it only reappears when an order brings a product not found in the catalog.

    Deleting the service category while it still has cards deletes those cards too. Lines of already imported orders stay: the name, SKU, price and quantity are stored in the line itself. But the line loses its link to the card, and the next order with the same product creates a new card in a new service category.

    If half-empty duplicates have already piled up, merge each one with the real card in the “Catalog duplicates” window, if the window found such a pair:

    • during a merge, orders, documents, stock movements and the link to the Forte product move to the card that stays, and the other one is deleted;
    • before clicking “Merge cards”, check which card the window marked as “Stays”: cards with order lines get a higher score, so the half-empty one may be the one that stays — the “Keep the other one” button swaps them;
    • after the merge, later Forte orders with this product go to the card that stayed.

    You can't undo a card merge — check the pair before clicking “Merge cards”.

    To keep duplicates from appearing, keep your catalog filled in and make sure SKUs on the marketplace match the product SKUs in Elbuz.

    Which status and payment type the document gets

    Forte status mapping is built into the connection itself — there's nothing to configure:

    Status in ForteDocument status in Elbuz
    newNew
    awaiting seller confirmationApproval
    awaiting bank confirmationApproval
    confirmed by sellerConfirmation
    out for deliveryShipped
    awaiting pickupShipped
    deliveredDelivered
    handed overDone
    canceled — by the seller, the bank or the buyerCanceled
    returnReturned

    Elbuz recognizes a Forte status the connection doesn't know by its name — for example, one containing «скасов» (“cancel”) becomes “Canceled”; if not recognized, it becomes “New” (mapping order).

    The “Related settings” card has buttons for manual mapping of statuses, payment types and delivery. Rules from these windows don't affect Forte orders: the import only uses rules tied to its own template, and the windows opened from the Forte card save rules without that tie. Rules of other templates and other marketplaces don't apply either.

    Installments and credit

    A large share of Forte orders is placed in installments or on bank credit. The payment method arrives as a name, and Elbuz recognizes these two cases in it:

    • the name contains the word «Рассрочка» (installment) — payment type “Installment”;
    • the name contains the word «Кредит» (credit) — payment type “Credit”;
    • other payment methods are matched by the general rules on words in the name, and with no match the type is “Bank card”.

    The payment status of every Forte order is set to “Pending”: you mark the actual receipt of money yourself once the bank transfers the funds.

    Automatic import

    Forte doesn't send instant notifications, so Elbuz contacts it by itself: the system task “Marketplace orders” picks up orders for all active Forte templates with a token every 5 minutes. The template needs no schedule — there's no “Schedule setup” button in the form. You change the interval in the “Job schedule” window, in this task's row.

    If another template is being imported at that minute, including manually, the pass is silently skipped and the next one picks up the orders. A disabled template is skipped by automatic import — disable or delete.

    What each run picks up

    In one run Elbuz picks up up to a thousand most recent orders, sorted by modification date from newest to oldest. There's no separate “new only” filter: the marketplace returns the general list, and Elbuz itself selects what it doesn't have yet. If your account has more than a thousand orders, the oldest ones won't make it into this batch.

    No duplicate is created: an order is recognized by its external number. Already imported orders get their status, payment and delivery updated while the order is among the thousand most recent. Your status changes only after a new change on Forte — who overwrites whom.

    Without a token no request is sent to Forte, but the log still ends with “Data import completed!”. After a stop, the last log line is “Operation aborted by user!”. If Forte rejected the key or the request failed, the log shows a red “Forte: API error —” line and no orders are saved. Then each order goes through one fork: one already imported from Forte gets its status, payment and delivery updated, a new one gets a document, and unknown items first become cards in the service category.
    noyesyesnonoyesnoyesyesnonoyesTemplate run“Token” field filled in?“API token not specified”no request is sent to ForteStop clicked?“Operation aborted by user!”no “completed” lineRequest to Forteup to 1000 most recent ordersForte accepted the key andresponded?Red “Forte: API error —” lineorders are not saved“Data import completed!”Marketplace returned orders?Order already amongthose imported from Forte?Status, paymentand delivery are updatedItem found in the catalog?New card in the service categoryBuyer and a “Customer order”document with lines
    • Start or end
    • Action or result
    • Decision: the path depends on the answer

    How to check that orders arrived

    After a run, these lines appear in the template log, in this order:

    • “Requesting a list of orders #1” — Elbuz contacted Forte.
    • “Orders received: N” — how many orders the marketplace returned. This includes orders imported earlier, so the number isn't the count of new ones.
    • “Total items imported: N” — how many new cards were created in the service category. The line is missing if all items were found in the catalog. When cards are created, it's followed by “Product indexing”.
    • “Total orders imported: N” — how many new documents were created. The line is missing if there were no new orders.
    • “Data import completed!” and the time taken.

    The log keeps no separate “skipped” or “failed” counters. Already known orders show up as the difference between “Orders received” and “Total orders imported”. Access errors are covered in the troubleshooting table.

    If a run broke off or was stopped

    A run goes like this: one request to Forte for a list of up to a thousand orders, then finding and creating buyers, then creating cards for unknown products, then documents. All new documents of the run are written with one database query, and their lines with the next one.

    There's no separate resume point. Each run asks for the same thousand most recent orders again and creates only those not yet among the ones imported from Forte — they're recognized by the external order number. So a repeat run after a break doesn't duplicate documents already created.

    • A break before documents are written — no new orders appear in Elbuz; a repeat run creates them from scratch. Buyers and cards created before the break are found on the repeat run, not created again.
    • A break between writing documents and writing their lines — the documents exist but have no line items. A repeat run treats them as imported and doesn't add the lines. You'll have to fill them in manually or delete them: the next run re-imports a deleted order if it's still among the thousand most recent.

    A stop of the Forte import is checked only once — before the request to the marketplace. If you click it before that point, the log says “Operation aborted by user!” and nothing is saved. If the request has already gone out, the orders are saved anyway, but there's no “Data import completed!” line at the end.

    Scenarios

    Handle Forte orders in a shared queue without losing manager edits

    Task: Forte orders should be processed in the same place as sales from other channels, and the manager keeps changing order status and contents in Elbuz.

    What to turn on: an “API — market.forte.kz” template and the key in the “Token” field. No schedule is needed.

    Result: every 5 minutes a run creates “Customer order” documents for new orders and updates status, payment and delivery in already imported ones. The manager's status changes only after a new change on Forte, including a cancellation.

    Tell installment and credit orders apart

    Task: see which orders are paid through a bank and not mix them up with the rest.

    What to turn on: nothing — recognition is built into the connection.

    Result: documents get the “Installment” or “Credit” payment type based on the payment method name, and the payment status is “Pending”. You mark the money as received yourself once the bank transfers the funds.

    Make line items land on existing cards, not new ones

    Task: products from Forte orders should be linked to your catalog cards.

    What to do: make sure the product SKU and name on Forte match the SKU and name of the card in Elbuz.

    Result: a matched item refers to the existing card. An unmatched one becomes a card in the service category — disabled, without the export flag, description or photos — and doesn't get into your category tree until you move it.

    What to do when orders don't arrive

    Troubleshooting common problems
    What you seeWhyWhat to do
    A red “Forte: API error —” line after “Requesting a list of orders #1” The marketplace rejected the key or the request failed; Forte's explanation is next to it Copy the key from your account again — in full, without spaces at the start or end (where to get it)
    “API token not specified” The “Token” field is empty, no request was sent to Forte Paste the token and save the template (how to connect)
    No “Orders received” line after “Requesting a list of orders” The marketplace returned no orders — there are none in the account Check the orders in your Forte account
    Old orders are missing in Elbuz A run picks up up to a thousand most recent orders Don't put off the first connection, and don't leave the template turned off for long (what a run picks up)
    Line items create new cards every time The SKU on the marketplace doesn't match the SKU in the catalog Compare SKUs and merge existing duplicates (service category)
    The order was canceled on Forte, but Elbuz shows the old status The order is no longer among the thousand most recent, or the pass hasn't run yet Wait up to 5 minutes; change an old order to “Canceled” manually (stock and reservation)
    An order document with no line items The run broke off between writing documents and their lines Fill in the line items manually or delete the document (run break-off)

    FAQ

    Where do I get a Forte Market token?

    In your seller account, in the API section. If the button you need isn't there, contact your Forte manager — API access isn't opened automatically for every account type.

    Can I import products from Forte into the catalog?

    No. This connection brings only orders; products arrive as order lines, and unknown items become cards in the service category.

    The bank transferred the installment money — why is the payment still “Pending”?

    Elbuz sets “Pending” for all Forte orders and doesn't mark payment as received. Record the bank's payment in the document yourself (installments and credit).

    Why doesn't the order status in Elbuz follow the marketplace?

    It does, while the order is among the thousand most recent: a run updates status, payment and delivery. Your status changes only after a new change on Forte (who overwrites whom).

    Do I need to set up status mapping?

    No, it's built in. Manual rules from the “Related settings” card don't affect Forte orders (status table).

    How do I remove orders imported by mistake?

    Filter the order list by the “Source: name” column and delete the documents in bulk. The next run imports them again if they're still among the thousand most recent (general procedure).

    Where it is and who has access

    Menu
    Directories → Operations → Data import
    Template type
    “API — market.forte.kz”
    Access right
    the “Import” window in “Group permissions”
    Have ready
    a token (API key) from your Forte Market seller account

    You don't need a file: the connection works with a key. One template is one connection to one seller account.

    Connection card of the API - market.forte.kz import template with the Token field
    1Token field
    1. Token field — the API key from the seller account.

    Related topics

    • If you need the big picture of how orders from different marketplaces become documents — Order import via API.
    • If you need to post orders and reserve products — Customer order.
    • If half-empty duplicates have piled up in the catalog — Catalog duplicates.

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free