ERP synchronization

Every order is pushed to the connected ERP, and a record of each attempt is kept, with the request sent, the response received and a button to retry when something fails.

Step by step

See why an order failed to sync

1. In the side menu, go to Sales → Orders. The ERP column shows you at a glance how each order's last attempt went.
2. Open an order with ERROR.
3. Scroll down to the ERP log card.
4. Click the log row to expand it. You will see the REQUEST that was sent and the RESPONSE the ERP returned.
5. Read the response message: it almost always says exactly what needs fixing.
6. Fix the data in the ERP and tap Reintentar on that row.

Check whether your integration is alive

1. In the side menu, go to Configuration → ERP.
2. Scroll down to the Integration activity panel.
3. At the top you will see Last push received and Last communication sent, with how long ago each one was.
4. Below there is a timeline of events, filterable with the All, Received, Sent and Errors chips.
5. Click an event to see its detail.

This panel is the direct answer to "is my ERP still connected?". If your ERP pushes data to the store and never has, a red notice says so.

Available ERPs

The Configuration → ERP selector offers these integrations:

• Contabilium
• Dragonfish — via Dragonfish Bridge, a desktop application that connects the local ERP to the platform.
• DUX
• Virtual Seller
• Ninox
• Acqua
• SAAS
• Bling — Brazilian stores only.

Besides the ERP list, the selector offers Dragonfish Bridge and API Token for your own integrations.

NonSistemas keeps working on accounts that already had it configured, but it does not appear in the selector for new accounts.

Each ERP has its own configuration article with its fields and its behavior.

The sync statuses

The ERP column in the listing shows the result of each order's last log:

• OK (green) — the operation completed and the ERP confirmed it.
• ERROR (red) — the operation failed. In the order detail, that log has the Reintentar button.
• ... (amber) — there is a record of the call but no response ever arrived. This is not a normal wait: it means the operation was cut off midway. Treat it as a case to review, not as something that will resolve itself.

The listing does not reorder orders with errors. The default order is by order number, newest to oldest. To find them, scan the ERP column or filter by whatever you need.

The order's log card

Each row shows:

• The status with its color: Exitoso, Error or Pendiente.
• The ERP name.
• The operation that ran.
• The ERP id the ERP assigned to the resource, if it returned one.
• The sent date and the duration in milliseconds. Above 5000 ms it is flagged in red.

Expanding the row reveals the full, formatted REQUEST and RESPONSE.

Watch out for one detail that trips people up: request and response are stored in EDN format, not JSON. They read just as well, but if you compare them character by character against your ERP's JSON documentation you will see syntax differences that are not a problem.

What Reintentar actually does

Reintentar re-runs that order's complete sync, regardless of which log row you clicked. It does not replay only the specific operation that failed.

After tapping it, reload the screen to see the new log: the card does not refresh itself today, which makes it feel like nothing happened.

Sending an order to the ERP on demand

At the bottom of the order detail, some accounts have the Send to ERP button, which pushes the order right then. It is not the same as Reintentar: this one works even if the order has no error log at all. It is enabled per account, so it does not appear in every store with an ERP configured.

A sync in progress cannot be stopped

There is no button to halt a sync that has already started. What you can do is switch off specific functions before they run: each ERP's configuration has per-function switches, for example turning off stock updates in DUX, or product and photo sync in Bling. The full cut-off is removing the ERP credentials.

Most common errors

• Product not found in the ERP — check that the code or SKU matches.
• Buyer not registered — create the customer in the ERP or sync them first.
• Expired credentials — renew the token in Configuration → ERP.
• Missing tax fields on the buyer — tax ID or tax condition not filled in.

If you cannot find it

• You cannot see Configuration → ERP. You have to be an administrator, or a manager with the ERP permission.
• You cannot see the logs or the Reintentar button. You need the Orders permission.
• You cannot see the ERP column in the listing. It only appears if you have an ERP connected.
• You cannot see the Send to ERP button. It is enabled per account.
• You cannot see Bling in the selector. It is only available for Brazilian stores.
• The activity panel says a push was never received. Check that the ERP webhook is configured with the values shown on that same configuration screen.