Acqua is an enterprise management system designed for wholesale businesses and distributors, with features for customer management, stock control, pricing, and commercial transactions. By connecting your VentasxMayor store with Acqua, wholesale orders are sent as transactions, stock and prices are kept up to date, and customers are automatically created in Acqua when they place their first order.
How it works
From Integrations > ERP select Acqua and enter your instance name along with your access credentials. VentasxMayor connects to Acqua using a two-level authentication system:
- A read token (public) for querying stock and prices.
- A write token (with credentials) for sending orders and creating customers.
Communication is bidirectional:
- Orders and customers flow from VentasxMayor to Acqua.
- Stock and prices flow from Acqua to VentasxMayor.
Configuration fields
| Field | Type | Required | Description |
|---|---|---|---|
| Instance | Text | Yes | Your Acqua instance name. This is the identifier that Acqua assigns to your company. Example: "Beauties". This value is used to build the API connection URL. |
| Username | Text | Yes | Username for your Acqua instance. Used to obtain the write token that allows sending orders and creating customers. |
| Password | Text | Yes | Password associated with the instance user. |
What syncs
Orders (VentasxMayor → Acqua)
Each confirmed order is sent to Acqua as a commercial transaction:
- Buyer data (name, tax ID, address, phone, email)
- Product list with SKU code, quantity, unit price, and discounts
- Payment terms and notes
- If the customer does not exist in Acqua, they are automatically created before the order is registered
Stock (Acqua → VentasxMayor)
Stock levels are queried from Acqua and updated in your wholesale catalog. Products are matched by SKU code.
Prices (Acqua → VentasxMayor)
Wholesale prices are obtained from Acqua and applied to the corresponding products in your online store.
Customers (VentasxMayor → Acqua)
When a wholesale buyer places their first order, VentasxMayor automatically creates the customer in Acqua:
- The system automatically determines whether the customer's document is a personal ID (DNI) or a business tax ID (CUIT) based on its format.
- All buyer data is sent (name, document, address, phone, email).
- For subsequent orders from the same buyer, the existing customer record in Acqua is used.
Sync behavior
Orders
- Mode: Automatic on order confirmation.
- Method: Orders are sent as POST transactions to the Acqua API.
- Retries: If Acqua responds with a 409 error (conflict), the system automatically retries up to 5 times. This can happen when there are concurrent operations on the same record.
- Customer creation: If the customer does not exist in Acqua, they are created before the order is sent. This process is automatic and transparent.
Stock and prices
- Mode: On demand via API queries.
- Authentication: Stock and price queries use a public read JWT token that does not require credentials. The token is obtained automatically.
Two-level authentication
- Read token: Obtained without credentials, allows querying stock and prices. It is public and freely accessible.
- Write token: Obtained with username and password, allows sending orders and creating customers. Required for all write operations.
Document type determination
- The system automatically determines whether the buyer's document is a personal ID (DNI) or a business tax ID (CUIT) by analyzing its format. This ensures the customer is registered correctly in Acqua.
Tips
- Verify that the Instance name is exactly as assigned by Acqua. An incorrect name will prevent all communication with the API.
- Make sure the user credentials have write permissions in Acqua. Without these permissions, stock queries will work but orders will not be sent.
- Automatic customer creation simplifies operations, but periodically verify in Acqua that customer data is correct, especially the document type (DNI vs. CUIT).
- If you see frequent 409 errors, it may indicate concurrent operations in Acqua. The system retries up to 5 times, but if the problem persists, consult your Acqua administrator.
- Run stock syncs frequently to avoid selling products that are not available. This is especially important in wholesale operations where order volumes are high.
- Orders are sent as complete transactions. Verify that your product data (SKU codes, prices) matches between VentasxMayor and Acqua to avoid rejections.