Acqua is a business management ERP aimed at wholesalers and distributors. With the integration on, your store's orders are recorded as transactions in Acqua, new customers are created automatically, and Acqua's price and stock update your catalog.
Step by step
- In the side menu go to Settings → ERP and pick Acqua.
- Fill in Instance: the name Acqua assigned to your company, for example
Beauties. The API address is built from that value, so it has to be exact. - Fill in User and Password for your instance.
- Decide whether to turn on Send discounts to Acqua (see below).
- Click Verify Configuration.
- Save. Once Instance, User and Password are filled in, the Sync Support block appears.
The connection uses two different credentials: a read token, obtained without user or password, used to query stock and prices, and a write token, obtained with your user and password, which is what allows sending orders and creating customers. That is why, if the user has no write permission in Acqua, stock still updates but orders do not go out.
The "Send discounts to Acqua" field
Off by default. When on, discounts and payment-method surcharges travel as a modifier line on the order, and the payment method travels with it. When off, the order goes out exactly as it did before the discount engine, without that line and without the payment method.
Item notes always travel, whichever way you set the switch.
What syncs and in which direction
| What | Direction | When |
|---|---|---|
| Orders | Store → Acqua | On confirmation, and again if you edit and save the order |
| Customers | Store → Acqua | If the buyer does not exist, they are created before the order is recorded |
| Price and stock | Acqua → Store | Automatically once an hour, and with Update all products |
Per-list prices. Acqua returns one price for each of its lists, and we apply them to the lists in your business that match by code. It is not a single price.
The sync never creates products. An item that exists in Acqua and not in your catalog is discarded. Load it into the store first, with the same code.
If you cannot find it or it does not sync
- A product is flagged "Not synced" even though it exists in Acqua. Acqua drops items with no price from the listing. If the item has no price loaded, it does not come through in the feed and gets flagged. Load the price in Acqua and sync again. See the detail of the warning in the ERP integration article.
- A customer was created with the wrong document type. The document type is decided by a simple rule: if the identification has a hyphen it is sent as CUIT; if not, as DNI. A CUIT loaded without hyphens is sent as a DNI. Always load CUIT numbers with hyphens (
30-12345678-9). - Stock updates but orders do not go out. The configured user has no write permission in Acqua. That is the direct consequence of the two-token model.
- 409 errors when sending an order. These are conflicts from simultaneous operations on the same record. We retry up to 5 times, one second apart. If the problem persists, take it up with your Acqua administrator.
- Nothing talks to Acqua at all. Check the Instance name: with a misspelled name the API address does not exist and everything fails.
- An order did not arrive. The error stays in the order's own log, with the Retry button, and in Integration activity.