ERP integrations connect your ERP or accounting system (such as Tally, Zoho Books, Marg ERP, or Vyapar) with Base.com to synchronise orders, stock, prices, products, and sales documents. When something goes wrong, the cause usually falls into one of a few predictable categories. This article covers the most common challenges and how to resolve them.
1. Wrong synchronisation direction
Not every ERP integration works both ways. In most setups, the ERP is the master system, and Base.com receives data from it. Assuming data flows in both directions when it does not will cause updates to be lost silently.
Solution
Before configuring the integration, define which system owns each data type:
- Stock levels
- Prices
- Product data
- Orders
- Invoices and documents
2. Product matching errors
Products fail to sync because identifiers differ between the ERP and Base.com. This typically causes errors such as product not found or document line items being empty.
Solution
- Use a consistent identifier (SKU or EAN) in both systems before connecting them.
- Select the correct matching method in the ERP integration settings.
- If importing products from the ERP, link them to existing Base.com catalogue entries before enabling sync.
- Avoid changing SKU or EAN values after products are already linked.
3. Stock or price synchronisation stops working
Sync appears to have been working but stops updating. Common causes include a connector application no longer running, incorrect warehouse or price group selected, or network or firewall issues blocking the connection.
Solution
- Confirm the integration is still authenticated and connected in Base.com.
- Check that the correct warehouse and price group are selected in the integration settings.
- If using a local connector application, verify it is running continuously and the host machine is not entering sleep mode.
- Review sync logs in the integration settings for specific error messages.
- Confirm that required ports and API endpoints are not blocked by a firewall.
4. Empty mapping lists
Payment types, warehouses, delivery methods, or numbering series are missing from the integration settings. This usually means the integration has not yet fetched the available options from the ERP.
Solution
- Open the integration settings and look for an option to fetch or refresh data from the ERP.
- Complete all mapping fields: payment methods, warehouses, delivery methods, and document numbering series.
- Set a default fallback for any payment or delivery methods that cannot be matched exactly.
5. Invoice or document is not created in ERP
A document fails to appear in the ERP after export. This is usually caused by the document not yet existing in Base.com, incomplete customer data, unmatched products, or forwarding being triggered before the ERP is ready to receive it.
Solution
- Verify the invoice or document exists in Base.com before triggering export.
- Check that customer invoice data is complete (company name, GSTIN, or first and last name for individuals).
- Confirm product matching is working correctly.
- Check numbering series mapping.
- Use status-based forwarding if the ERP needs time to generate the document before the next automation step runs.
- Enable error-stopping logic in automatic actions so the process does not continue if the export fails.
ERP integration best practices checklist
Where to find ERP integrations in Base.com
ERP and accounting integrations are configured in the Base panel under Integrations → Add integration → Accounting / ERP.