Integrate your wholesale store on VentasxMayor with the Ninox ERP to automatically sync orders, stock, and prices. Ninox offers an enterprise management solution with specific features for the wholesale market, including product variant management and Argentine fiscal conditions.
How it works
From API Integrations > Ninox select Ninox 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 Ninox catalog are reflected in your online store.
The Ninox integration is straightforward: you only need an authentication token to start syncing.
How to activate the integration
Activating Ninox is not self-service. The flow is:
- Contact Ninox sales to register the integration with VentasxMayor. Their team will issue you an API token.
- Coordinate with your VentasxMayor account executive and hand over the token. Support performs the initial activation and leaves the sync running automatically.
- Before activation, align your catalog: load products in VentasxMayor with the same SKU, price, and stock they have in Ninox. This avoids mismatches the moment the sync turns on.
Once active, prices and stock are managed from Ninox. Update prices and stock only from Ninox; any change you make in VentasxMayor will be overwritten by the next sync.
Configuration fields
- Token (text, required): Ninox API authentication token. Used to validate every request sent to the system. Provided by the Ninox team when the integration is registered.
After pasting the token, use the Verify Configuration button to confirm the connection works before operating.
What syncs
Orders (VentasxMayor → Ninox)
Each confirmed order in your store is automatically sent to Ninox. The order includes:
- Complete buyer data (business name, tax ID, address, fiscal status)
- Detailed breakdown of each product with quantities, unit prices, and subtotals
- Buyer's fiscal condition mapped to the corresponding Ninox code
- Notes and payment terms
- Subtotal, total discount, surcharge, and shipping cost as separate order fields
When an order is successfully submitted, Ninox returns an invoice ID that is stored as the ERP reference in VentasxMayor. This links each order with its corresponding record in Ninox for tracking and traceability.
Stock (Ninox → VentasxMayor)
Inventory levels are imported from Ninox to your store. The sync uses two specialized endpoints:
- GetData: retrieves base product and stock data
- GetDataCurva: retrieves bulk product data for large catalog synchronization
Ninox can also push updates to VentasxMayor through an authenticated webhook using the same token, allowing stock and price changes to be reflected near real-time.
Prices (Ninox → VentasxMayor)
Prices are imported from the Ninox product catalog. Prices are updated alongside stock sync to maintain consistency between inventory and pricing in your wholesale store.
Sync behavior
Order submission
Orders are sent via an HTTP POST request to the Ninox API. The response includes a Ninox invoice ID that is stored as the ERP reference in VentasxMayor. This reference allows tracking each order across both systems.
Order cancellation
Ninox supports order cancellation via a dedicated endpoint. If an order needs to be cancelled after being sent to the ERP, the system communicates the cancellation directly to Ninox using the stored invoice reference.
Product codes
Products without variants are identified by their numeric SKU. Products with variants use the articuloId!talleId!colorId format as their identifier code. This format allows Ninox to correctly identify each combination of article, size, and color with its record in the ERP.
Fiscal condition mapping
Customer fiscal conditions are mapped to Ninox numeric codes:
- 1 = Final Consumer (CF)
- 2 = Registered Taxpayer (RI)
- 3 = Monotributo (simplified tax regime)
- 4 = Tax Exempt
For Final Consumer, the customer's DNI is sent; for the rest, the CUIT is sent. This mapping ensures each order reaches Ninox with the correct buyer fiscal condition, which is essential for invoicing and tax compliance.
Bulk stock sync
Stock sync uses the GetData and GetDataCurva endpoints to retrieve product data in bulk. This allows efficient processing of large catalogs, updating stock and prices for all products in a single operation.
Tips
- Before activating the integration, verify your store's catalog and Ninox's catalog match on SKU, price, and stock. Differences in these fields cause mismatches the moment sync turns on.
- Once integrated, do not edit prices or stock from VentasxMayor. Make changes only in Ninox so your edits are not overwritten by the next sync.
- Verify that the API token is valid and current. An expired token will stop all order, stock, and price synchronization. Use the Verify Configuration button after any change.
- Make sure your customers' fiscal conditions are correctly configured in VentasxMayor. An incorrect mapping can cause invoicing issues in Ninox.
- If you have products with size and color variants, verify that codes in the
articuloId!talleId!colorIdformat match between both systems to avoid stock discrepancies. - Keep the Ninox invoice reference stored with each order. This reference is key for traceability and troubleshooting between systems.
- Check the error log periodically. An order that does not reach Ninox can delay invoicing and merchandise dispatch.
- Before cancelling an order that has already been sent to Ninox, verify that cancellation is possible according to your business policies and the order's status in the ERP.