VentasxMayor syncs every order with the wholesale business's ERP so the operation is automatically reflected in the management system: stock, prices, invoices, account balance. The integration runs over API and keeps a detailed log of every attempt, with the ability to retry manually when something fails.
Supported ERPs
The platform has native integration with eight ERPs, each one with its own configuration doc:
- Contabilium — direct API sync.
- Dragonfish — via Dragonfish Bridge (desktop application that connects the local ERP to the platform).
- DUX Software — direct API sync.
- Salesforce / Virtual Seller — direct API sync.
- Ninox — direct API sync.
- NonSistemas — direct API sync.
- Acqua — direct API sync.
- SaaS UE — direct API sync.
The ERP choice is configured in Settings → Integrations → ERP and each one's details (fields, what gets synced, behavior) are in its specific section.
Sync states
Every time the platform tries to send or receive data from the ERP, an entry (an "ERP log") is recorded with a state:
- OK (✅ green) — the operation completed successfully and the ERP confirmed. In the code it maps to
:success. - ERROR (❌ red) — the operation failed. The platform shows the error in the log and enables the "Retry" button.
- PENDING (🟡 yellow) — the operation was sent but the ERP response hasn't arrived yet. Resolves to OK or ERROR once the confirmation comes back.
In the orders list, the ERP column shows the latest log status per order. Orders in error usually float to the top with a red visual indicator so the team can prioritize them.
Order ERP logs screen
From an order's detail you access ERP Logs, which lists every sync attempt with:
- Status (Successful / Error / Pending) with the matching color.
- ERP type (Contabilium, DUX, etc.).
- Operation executed (for example: create order, update stock).
- ERP id — the identifier the ERP assigned to the resource, when available.
- Sent at and duration (in milliseconds; over 5000 ms is highlighted red).
- Request — the JSON payload the platform sent to the ERP, expandable and formatted.
- Response — the response the ERP returned, expandable and formatted. Shown in red on errors.
Each log has a toggle to expand/collapse the detail. Logs with status Error show a Retry button that fires the operation again; useful after fixing a data point in the ERP (a missing product code, an unregistered customer, an expired credential).
Available actions
- View ERP logs of the order: chronological list of every sync attempt with detailed request/response.
- Expand/collapse log: shows the full JSON of the request and the ERP response.
- Retry sync: relaunches the failed operation from an error log, without having to edit the order.
- See status in the list: the ERP column shows OK / ERROR / PENDING to quickly spot which orders need attention.
Tips
- Review the list of orders with status ERROR at least once a day — in high-volume wholesale operations, accumulated errors create stock and collection mismatches with the ERP.
- The most common errors are: product not found in the ERP (review SKU/code), buyer not registered (sync or create them first in the ERP), expired credentials (renew the integration token), and missing buyer fields (tax ID, tax status).
- Before retrying, open the log and check the ERP response — the message usually states exactly what to fix.
- If a sync consistently takes longer than 5 seconds, it can be a network issue or an overloaded ERP. Coordinate bulk-sync windows to avoid clashing with other ERP processes.
- For integrations without a direct API (when a customer runs an unsupported ERP), Dragonfish Bridge is the usual path: it's installed on a PC at the business site and bridges the local ERP with the platform.
- Manual order exports to Excel/CSV (in the orders list) are different from ERP integration — they help when there is no automatic sync or as a backup. Some bespoke exports (custom formats like Jesus Fernandez, Decimo Arte, Karina, etc.) are only enabled for specific businesses through admin-level platform configuration.