When the ERP sends data to Rezomatic
Sending is automatic; it is triggered by every operation on a stock unit or variant:
| Event | Effect on the Rezomatic side |
|---|---|
| Creation of a stock unit | Creates the item at the point of sale. |
| Modification of a stock unit | Updates the item at the point of sale. |
| Deletion of a stock unit | Removes the item from the point of sale. |
| Restoration of a stock unit (from trash) | Recreates the item at the point of sale. |
| Price change on a variant | Updates all units linked to that variant. |
| Creation / modification of a customer | Creates or updates the customer record. |
Data sent to Rezomatic
For each item, the ERP sends:
| Data | Source |
|---|---|
| Item code | Internal reference (barcode) of the stock unit. |
| Name | Product title (special characters are cleaned up automatically). |
| City | Location city. |
| Location | Shelf / bin location. |
| Purchase price excl. VAT | Purchase price excl. VAT entered on the unit. |
| VAT rate | Sales VAT rate for the variant (or the configured margin VAT rate if not set). |
| Price incl. VAT | The variant's promo price if lower than the public price, otherwise the public price. |
| Size / color | Variant attributes. |
| Arrival date | Date the item entered stock. |
| Product type | New or used, determined automatically from the purchase VAT (margin VAT → used). |
| Product condition | The "Condition" attribute (New, Used…). |
| Supplier | Supplier identifier. |
| Item URL | Direct link to the stock sheet in the ERP (salespeople can view it from the till). |
| Description | Model description. |
Conditions for reliable synchronization
For an item to correctly flow from the ERP to Rezomatic, several conditions must be met at the tenant, model, variant, and stock level.
On the tenant / configuration side
- The Store module must be enabled on your subscription.
- The URL and API key for your Rezomatic point of sale must be entered (initial setup done by support when the service is activated).
Without these two conditions, no synchronization is triggered at all.
On the model (catalog) side
- Product name filled in.
- SKU filled in.
On the variant (product) side
- Public price > 0 or Promo price > 0 (the most relevant price is sent to Rezomatic).
- Sales VAT filled in (used for the VAT calculation at the till).
- Size filled in.
On the stock (physical unit) side
| Condition | Effect if missing |
|---|---|
| Purchase VAT filled in | Blocking: without a purchase VAT rate, the unit is not sent to Rezomatic. |
| Internal reference generated | Always present (automatically generated on creation). |
| City filled in | Without a city, the item is sent with "No city". |
| Location filled in | Without a location, the item is sent with "No location". |
| Product condition filled in | Without a condition, the item is sent with "No condition specified". |
| Supplier filled in | Recommended for traceability. |
| Stock entry date | Always present (generated on creation). |
Good to know — If a piece of data is missing, the unit is still sent to Rezomatic in most cases (with a default value), except for the purchase VAT, which completely blocks synchronization. Always check this field during an import or manual entry.
Checking that an item is properly synchronized
Two ways to check:
- On the Rezomatic side: search for the reference (barcode) or SKU in the catalog. If the item appears with the correct information, synchronization is working.
- On the ERP side: go to Tools > Rezomatik Logs (see next section) to view the history of sends and any errors.