Ninox manages your inventory and your invoicing. It is the only integration that brings the whole catalog from the ERP: products, variants, prices and stock. Store orders travel to Ninox to be invoiced.
Step by step
- Ask Ninox for the token when you set up the integration.
- In VentasxMayor go to Settings → ERP, pick Ninox and paste the Token.
- Click Verify Configuration to confirm the connection.
- Before importing, create one list in Settings → Price lists for each price you use in Ninox, with the exact code
L2,L3,L4orL5. See the table below. - Pass your Ninox support team the three values from the Webhook configuration data box so they enable automatic stock and price pushes.
- Click Import Ninox Products to bring in the catalog.
Only one token is valid at a time. If Ninox generates a new one, the previous one stops working and orders bounce with "No se encontró la integración". Watch out for stale browser tabs too: if you save any change from a tab that was open earlier, the token that tab had loaded gets written back and overwrites the good one.
Price lists (do this before importing)
Ninox handles up to 5 prices per item. The mapping is fixed:
| Price in Ninox | Destination in VentasxMayor |
|---|---|
| Price 1 | Product price (the one the buyer sees) |
| Price 2 | List with code L2 |
| Price 3 | List with code L3 |
| Price 4 | List with code L4 |
| Price 5 | List with code L5 |
The code has to be exactly LN; the name is up to you. If a Ninox item has price N loaded and the LN list does not exist, the whole import fails with the error "Price list not found LN" and nothing is updated. Create every list you use in one go.
What syncs and in which direction
| What | Direction | When |
|---|---|---|
| Full catalog: name, description, per-list prices, variants and stock | Ninox → Store | When you click Import Ninox Products |
| Price and stock | Ninox → Store | When Ninox pushes over the webhook |
| Orders and cancellations | Store → Ninox | On confirmation and on voiding |
Categories are not imported by default. Ninox tags only carry the root category, so importing them would overwrite the subcategories you loaded by hand product by product. If you really want Ninox to send categories, tick Update categories from the file/ERP before importing. It will warn you that existing categories are replaced.
The import hides whatever did not come in the listing. Products in your catalog that Ninox does not send end up with no stock and hidden in the store. They are not deleted, and they show again on their own if they reappear in a later import. If products vanished after an import, this is why: check whether they are still loaded in Ninox.
Product codes: without variants, the option code is the Ninox item number followed by two exclamation marks (123456!!). With variants, the format is item!size!color using Ninox's internal identifiers. Do not edit them by hand: they are the key Ninox uses to recognize each order item.
Prices: Ninox does not handle per-variant prices, so the full price is loaded on each product option and the parent product's price stays at zero. That is expected and it does not change what the buyer sees.
Orders: they carry the buyer's data according to their tax condition, the detail with size, color and quantities, the subtotal, the total discount, the surcharge, the shipping and the total as separate fields, plus the addresses and the notes. If Ninox accepts it, it returns the invoice number, which is stored on the order as the ERP reference and is what is used later to cancel it.
Tax conditions: 1 Consumidor Final (DNI is sent), 2 Responsable Inscripto, 3 Monotributo and 4 Exento (all three send CUIT). A badly loaded mapping causes invoicing problems on the Ninox side.
If you cannot find it or it does not sync
| Message or symptom | Cause | Fix |
|---|---|---|
| "No se encontró la integración" | The saved token is not the one currently valid in Ninox. | Load the current token, use Verify Configuration and resend the orders that bounced. |
| "Price list not found LN" | There are items with price N and no list with code LN. | Create the list with the exact code and import again. |
| "No hay stock suficiente" when sending an order | Ninox validates stock on receipt and the real figure is lower than the order. | Import products to refresh stock, restock in Ninox or adjust the order, then resend it. |
| Prices or stock days out of date | The webhook was never configured on the Ninox side, or the token got overwritten. | Look at Integration activity: if Last push received says "Never", pass the Webhook configuration data to Ninox. If you see "Push rejected: the token does not match", update the token on both sides. |
| Products that vanished from the store | They did not come in the last import and got hidden. | Check they are still loaded in Ninox and import again. |
| Subcategories were wiped | The import ran with Update categories from the file/ERP ticked. | Load the subcategories again and leave the box unticked on future imports. |
Tips
- When setting up the integration, do not assume the webhook got configured. Ask Ninox to fire a test update and watch the activity panel until you see the first push received.
- Only one token is valid at a time: agree on who loads it and close stale configuration tabs.
- Once integrated, do not edit prices or stock from the store. The next sync overwrites them.
- Keep the invoice reference stored on each order: it is the link between the two systems.