Dragonfish is Zoo Logic's ERP and point of sale, widely used in Argentine wholesale apparel. With the integration on, your store's orders record themselves in Dragonfish, and Dragonfish's stock and prices update your catalog.
Step by step
- Ask Dragonfish for the API endpoint, the client code and the token.
- In VentasxMayor go to Settings → ERP and pick Dragonfish.
- Fill in the Endpoint with protocol, port and trailing slash. Example:
http://181.13.215.214:8015/api.Dragonfish/. - Fill in Client and Token.
- If you use a specific price list, type its exact name under Main list. We look it up by name to get the code.
- Click Verify Configuration.
- Save. Once Endpoint, Client and Token are filled in, the Sync Support block appears.
What goes in the "Client" field
The on-screen help says "default client code for orders", and that is confusing. It is not one of your buyers' codes. It is the identifier of your database or company inside Dragonfish: it travels on every API call as the IdCliente header. These are short values, like MAYORD or MITO. If you do not know yours, ask your Dragonfish support team for it along with the token.
Direct integration or Dragonfish Bridge
They are two separate, mutually exclusive cards in the selector. You pick one.
- Dragonfish (this one): we connect over the API straight to your installation. It requires the endpoint to be published to the internet, with the port open and forwarded.
- Dragonfish Bridge: a desktop app that runs on your computer, authenticates with the generic API token and does the job in reverse: the app periodically asks which orders are pending, marks them as synced, and pushes stock and prices. It does not need to expose anything to the internet, and it has to stay open while it syncs. It is not real time and it does not run alongside the direct integration.
If your Dragonfish sits behind a firewall you cannot open, the Bridge is the way.
What syncs and in which direction
| What | Direction | When |
|---|---|---|
| Orders | Store → Dragonfish | On confirmation, and again if you edit and save the order |
| Customers | Store → Dragonfish | If the buyer does not exist, they are created before the order is sent |
| Price and stock | Dragonfish → Store | Automatically once an hour, and with Update all products |
You do not need to force anything for day-to-day use. The hourly pass walks the whole catalog and also recalculates each product's "Not synced" warning.
Per-list prices. Dragonfish returns several price lists per item and we save all of them against the lists in your business that match by code, not just the one you set under Main list.
The sync never creates products. An item that exists in Dragonfish and not in your catalog is discarded. Load it into the store first.
Variant codes. Products with color and size use the format Article!Color!Size. If your codes do not follow that format, no match is made.
Customer creation. When a new buyer places their first order, we register them in Dragonfish: the hyphens are stripped from the identification and a code of up to 10 characters is built for them. There is no fiscal validation against AFIP; the data travels exactly as loaded in the store, so load it correctly.
If you cannot find it or it does not sync
- It stopped syncing all of a sudden. The most common causes are an expired token or an unreachable endpoint. Check from outside your network that the port answers, and use Verify Configuration.
- An order did not arrive. On a conflict (409 error) we retry up to 5 times, one second apart. If the error persists, it is logged on the order, with the Retry button, and in Integration activity. No email notice is sent to the merchant: the activity panel is where you look.
- Products with the "Not synced" triangle. See the ERP integration article. For Dragonfish it recalculates itself on every hourly pass.
- Prices from one list do not arrive. The list code in VentasxMayor has to match the one in Dragonfish. For the main list, the name also has to be spelled exactly.
- I use the Bridge and it does not sync. The app has to be open. Keep it updated.