ERP: Contabilium

Contabilium is a cloud-based accounting and commercial management system, widely used by wholesale businesses in Argentina for AFIP electronic invoicing, stock control, and sales management. By connecting your VentasxMayor store with Contabilium, wholesale orders are automatically sent to the management system in invoice-ready format, and stock and prices are kept up to date in your online catalog.

How it works

From Configuration > ERP select Contabilium and enter your ID, email, and API Key. Once connected, VentasxMayor communicates with Contabilium through its REST API:

• Orders flow from VentasxMayor to Contabilium each time a wholesale buyer confirms an order. The order arrives formatted and ready for invoice generation.
• Stock and prices flow from Contabilium to VentasxMayor automatically, grouping updates to optimize performance.

Before activating the integration

For the sync to work well from day one, align the data between both systems:

• Make sure each product in VentasxMayor has the same SKU (code) as in Contabilium. That is the only way the two systems can link products to each other.
• Verify that the initial price and stock values match on both sides before turning on the sync.
• If you manage specific warehouses or price lists in Contabilium, write down the exact names so you can use them when configuring the integration.

Configuration fields

After entering your data, you can use the Verify configuration button so VentasxMayor checks credentials, warehouse, and price list against the Contabilium API and shows you errors, warnings, and details before going live.

What syncs

Orders (VentasxMayor → Contabilium)

Each confirmed order is sent to Contabilium in invoice-ready format:

• Buyer data (first name, last name, CUIT/DNI tax ID, email, phone, address, city, province, country, postal code).
• Product list with SKU code, quantity, unit price, VAT, and discount.
• Payment and shipping surcharges as additional items when applicable.
• Order notes and issue date.
• Status is sent as Aceptada (Accepted) — or Cancelada (Canceled) if the order was cancelled in VentasxMayor.
• Discounts are applied at the item level or as a separate "Descuento" item depending on the configuration.
• Product codes are automatically sent in uppercase.

If you edit the order in VentasxMayor after confirmation and Contabilium has not yet processed it, the edit is automatically resent. Once you change the order status in Contabilium (for example, you invoice it, convert it to a quote, or edit the invoice), Contabilium will no longer accept further changes from VentasxMayor for that order. If you need to fix something after that point, you'll have to apply the change in both systems separately.

Stock (Contabilium → VentasxMayor)

Stock levels are queried from Contabilium and updated in your catalog. If you configured a specific warehouse, only that warehouse's stock is imported. Products are matched by SKU code.

Prices (Contabilium → VentasxMayor)

Wholesale prices are obtained from the price list configured in Contabilium. If you didn't configure a specific list, the default is used. Prices are adjusted according to the No Tax and Final price? settings.

Sync behavior

Orders

• Mode: Automatic on order confirmation.
• Timing: Immediately after the buyer confirms the order.
• Errors: Logged in the order's ERP log history. From the order detail you can retry the send manually using the retry button.

Stock and prices

• Change accumulation: When you save a product or when Contabilium notifies of changes, the affected SKUs are accumulated in an internal queue. A central process picks up that queue every 3 minutes and asks Contabilium for the updated data, instead of making one request per change.
• Sync on product create or edit: When you create a new product or edit any field of an active product, saving automatically requests price and stock from Contabilium.
• Scheduled background sync: A scheduled mass sync runs that walks the entire catalog against Contabilium, as a safety net for changes that may not have propagated.
• Pagination: Products are fetched from Contabilium in pages of 100, with a small pause between pages to avoid overloading the server.
• Rate limiting: If Contabilium responds with HTTP 429 (too many requests), VentasxMayor automatically retries up to 10 times with a 60-second pause between each attempt.
• Mismatch detection: During a mass sync, VentasxMayor identifies products that exist in your catalog but not in Contabilium and flags them as mismatched so you can review them.

Product codes

• SKU codes are automatically converted to uppercase before being sent to Contabilium. If your products have lowercase codes in VentasxMayor, they will arrive in uppercase in Contabilium.

Forcing a manual sync

Once the integration is connected, the ERP configuration screen shows a Sync Support section. From there you can:

• Update all products: triggers a mass sync against Contabilium. Pulls prices, stock, and product data from the ERP. The operation may take several minutes and cannot be interrupted; it may overwrite local changes.
• Update product (by SKU): enter a specific SKU code to sync only that product.

Before running either action, VentasxMayor asks for confirmation because the sync may overwrite changes made on the web.

Unified management in Contabilium

Once the integration is active, manage prices and stock only in Contabilium. Any change you make directly in VentasxMayor may be overwritten by the next sync. The practical rule: the ERP is the source of truth for price and stock; the online store reflects that data.

Tips

• Clearly define the Price List if you manage multiple lists in Contabilium. The wrong list can cause your buyers to see prices that don't correspond to your online wholesale channel.
• If you sell products to order or manufacture on demand, enable No Stock to prevent sales from being blocked due to unregistered ERP inventory.
• Use Discount in items if your invoicing team needs to see the discount applied to each individual product in Contabilium, instead of a separate line.
• Review the No Tax and Final price? settings carefully. An incorrect configuration can cause discrepancies between the price the buyer sees and what is recorded in Contabilium.
• Before changing an order's status in Contabilium, verify you don't need to make any further adjustments to the order from VentasxMayor. Once the status is changed, those changes will no longer sync.
• If you see frequent rate limit errors (429), it may be a sign that too many products are being updated at once. Consider running updates during off-peak hours.
• Keep in mind product codes are sent in uppercase. Make sure codes in Contabilium are in uppercase so they match correctly.