What each connection supports
A quick guide to the records each connection brings into Balta Labs.
On this page
The connections serve different jobs. A marketplace may show what was sold and shipped, while an ERP may hold the tax and cost records for the same sale. This guide compares what Balta Labs currently imports, not every feature offered by each platform. Available history and detail also depend on the account and its permissions.
At a glance
| Connection | Orders | Money and returns | Shipments or stock | VAT and OSS starting point |
|---|---|---|---|---|
| Shopify | Store orders | Refunds and payments | Fulfillment details and supported stock transfers | Order tax fields; review your store’s tax setup and origins |
| Amazon | Seller orders by selected marketplace | Financial transactions, sometimes later than the order | FBA shipments and supported stock transfers | Varies by marketplace and who is responsible for VAT |
| Allegro | Marketplace orders | Completed refunds and billing entries | Some fulfillment evidence; no transfer import | Some tax or ship-from details may be missing |
| bol | Marketplace orders with gross prices | Returns and settlement lines as evidence | Shipments; no transfer import | Seller VAT is not supplied by the bol order connection |
| weclapp | ERP sales orders | Recorded order tax and related ERP data | Articles, warehouses, and supported stock transfers | Useful tax source when sales are recorded and matched correctly |
These are broad checks, not a promise that every record is present for every order. A “supported” source can still have a missing field, delayed record, or shorter history.
Which source should you connect first?
For an order view, start with the platform where the customer placed the order. Add weclapp when it holds the corresponding sales, tax, article, or cost records. Balta Labs can link records of the same sale so that two sources do not automatically become two sales. Review the matches and decide which source should supply the amount used in a report. Follow the deduplication rule guide to preview a match before activating it.
For internal stock transfers, use weclapp, Shopify, or Amazon where the relevant movement data exists. Allegro and bol connections do not supply that transfer view. Marketplace shipments and customer returns are not the same thing as transfers between your own warehouses.
Check tax before exporting
An imported order is not automatically an OSS-ready order. The report needs reliable sales amounts, tax treatment, destination, and, where relevant, the country from which goods were dispatched. A missing field is a reason to review the source, not a zero tax amount. Shopify, Amazon, Allegro, and weclapp can offer different pieces of that picture, depending on the account and transaction.
Bol is the clearest case: its order total includes VAT, but the connection cannot determine the seller’s VAT from that total alone. Use the seller’s ERP, invoicing system, or another reviewed tax source for that figure. Bol settlement invoice VAT is about bol’s fees. The OSS review guide shows where to inspect gaps before using an export.
Expect different history and timing
Historical reach differs. Bol’s changed-order recovery is about three months and its settlement specifications about two years; Amazon financial records may arrive after the order. A first import can therefore show an order before all of its supporting records have arrived. Check Orders → Configuration → Sources for each stream’s coverage and errors, then inspect a few order details before trusting a period total.