ERP: Dragonfish

Integrate your wholesale store on VentasxMayor with the Dragonfish ERP to automatically sync orders, stock, prices, and customers. Dragonfish is a management system widely used in the Argentine wholesale market, and this integration allows your online operation and your management system to work in sync without manual intervention.

How it works

From Integrations > ERP select Dragonfish and fill in the configuration fields. Once connected, orders placed in your wholesale store are automatically sent to the ERP, and stock levels and prices from the ERP are reflected in your online catalog.

In addition to the standard integration, VentasxMayor offers a companion desktop application called Dragonfish Bridge (built with Tauri) that provides real-time bidirectional sync. This application runs on your computer and maintains continuous synchronization between Dragonfish and your wholesale store, ideal for operations that require immediate updates.

Configuration fields

• Endpoint (text, required): Dragonfish API endpoint URL. Must include the protocol and port. Example: http://181.13.215.214:8015/api.Dragonfish/. Make sure to include the trailing slash.
• Cliente (text, required): client ID provided by Dragonfish. This code identifies your company within the system.
• Token (text, required): JWT authentication token. Used to validate every request sent to the Dragonfish API. Request it from Dragonfish technical support or generate it from their admin panel.
• Lista (text, optional): price list name or code. If your company manages multiple wholesale price lists (for example, by channel, region, or customer category), enter the one you want to use for your online store. The system looks up the list by name to find the corresponding code.

What syncs

Orders (VentasxMayor → Dragonfish)

Each confirmed order in your store is automatically sent to Dragonfish. The order includes:

• Complete buyer data (business name, tax ID, address, fiscal status)
• Product details with quantities, unit prices, and subtotals
• Payment terms and notes

If the customer does not exist in Dragonfish, they are automatically created before the order is sent (see the customers section below).

Stock (Dragonfish → VentasxMayor)

Inventory levels are imported from Dragonfish to your store. The sync queries the stock and prices endpoint with pagination to efficiently process large catalogs.

Prices (Dragonfish → VentasxMayor)

Prices are imported from the configured price list. If you set the Lista field, the system looks up the list name to get the internal code and retrieves the corresponding prices. This allows you to maintain differentiated pricing for your online wholesale channel.

Customers (VentasxMayor → Dragonfish)

When a customer places an order and does not exist in Dragonfish, the system automatically creates them. The process includes:

• Fiscal data validation (tax ID, AFIP tax status)
• Sending complete customer information (business name, address, contact)
• Associating the created customer with the order

Sync behavior

Order submission

Orders are sent via a POST request to the /Pedido/ API endpoint. The system includes all the information needed so the order is registered in the ERP without manual data entry.

Stock and price sync

Stock and prices are retrieved from the Dragonfish ConsultaStockYPrecios endpoint via GET requests with pagination. This allows processing large catalogs without overloading the connection.

Automatic customer creation

Customers are created via a POST request to the /Cliente/ endpoint. The system validates fiscal data before submission to ensure the record is accepted by Dragonfish.

Product codes

Products with variants (color, size) use the Articulo!Color!Talle format as their identifier code. This format allows Dragonfish to correctly associate each product variant with its record in the ERP.

Automatic retries

If a sync fails with a conflict error (409 status code), the system automatically retries up to 5 times with a 1-second delay between attempts. This covers temporary concurrency situations in the ERP.

Error notifications

When persistent sync errors occur, the system sends email notifications so you can take action quickly.

Price list lookup

The system looks up the price list by name to find the corresponding internal code. This simplifies configuration since you do not need to know the numeric list code.

Tips

• Verify that the API endpoint is accessible from the internet. If your Dragonfish installation is behind a firewall, make sure the port is open and correctly forwarded.
• Keep the JWT token up to date. If the token expires, synchronization will stop and orders will not reach the ERP.
• If you use the Dragonfish Bridge app, keep it updated to ensure compatibility with the latest API versions. The app runs on your desktop and must be open for real-time sync to work.
• Run a manual sync after bulk changes in the ERP (such as price list updates or merchandise intake) to verify everything is correctly reflected in your store.
• If you have products with color and size variants, make sure the codes in Dragonfish follow the Articulo!Color!Talle format for correct matching.
• Check the error log periodically. An order that does not reach Dragonfish can delay merchandise preparation and dispatch.
• If you configure a price list, use the exact name as it appears in Dragonfish to avoid lookup errors.