Through the link between Optiply and Monta, newly placed orders in Optiply are reported in Monta, and deliveries from Monta are reported in Optiply.
Not only the purchase orders from Optiply are forwarded to Monta. All adjustments to orders made in Monta are reported in Optiply. As soon as all lines in Monta are stated as 'approved', the order will be closed in Optiply. The order will then automatically disappear from the 'to book' list in Optiply.
Overview
Entity | Direction | Update Frequency |
Products | Monta > Optiply | Every 30 min |
Product Deletions | Monta > Optiply | Every 30 min |
Suppliers | Monta > Optiply | Every 30 min |
Supplier Products | Monta > Optiply | Every 30 min |
Sell Orders | Monta > Optiply | Every 30 min |
Buy Orders | Optiply > Monta | Every 15 min |
Buy Orders | Monta > Optiply | Every 30 min |
Receipt Lines (Item Deliveries) | Monta > Optiply | Every 30 min |
MontaWMS suffers from internal server errors which result in errors in their API responses. Optiply’s retry mechanism can not catch these errors. Therefore desynchs might occur. Please contact Monta for a resolution to these problems.
Products
Optiply | Monta |
name |
|
skuCode |
|
eanCode |
|
price |
|
unlimitedStock |
|
stockLevel |
|
status | When product doesn't exist, status Disabled is given |
Products that are Inactive on Monta will not be pulled/synced to Optiply.
If the customer changes the status to Inactive for a product on Monta, this change will not be reflected in Optiply. Therefore the status needs to be changed manually in Optiply.
Suppliers
Optiply | Monta |
name |
|
| |
remoteId |
|
Supplier Products
Optiply | Monta |
name |
|
skuCode |
|
eanCode |
|
price |
|
lotSize |
|
supplierId |
|
productId |
|
status | enabled |
No Multiple SupplierProducts:
Each product can only have one SupplierCode in Monta, so it will have only one enabled SupplierProduct in Optiply as well.
If the SupplierCode is changed we will sync the new SupplierProduct and set the previous one with status = disabled.
Sell Orders
Optiply | Monta |
totalValue | 0 |
placed |
|
completed (*1) |
|
remoteId |
|
(*1) If Shipped date on Monta is empty, we’ll map complete with the Received date
We do not sync SellOrder changes in any way, order line changes, line deletions or new lines added to existing SellOrders will not be updated in Optiply.
Sell Order Lines
Optiply | Monta |
productId |
|
quantity |
|
subtotalValue | 0 |
Buy Orders (Optiply > Monta)
Optiply | Monta |
buyOrder.Id |
|
supplier.Id |
|
buyOrder.placed |
|
buyOrder.placed + supplier.deliveryTime |
|
The order numbers from Optiply are used in Montapacking to create new orders. Do not change these order numbers manually.
We check uncompleted and updated Purchase orders and validate if they exist in Montapacking.
Buy Order Lines (Optiply > Monta)
Optiply | Monta |
buyOrder.placed + supplier.deliveryTime |
|
skuCode |
|
quantity |
|
Buy Orders (Monta > Optiply)
Optiply | Monta |
buyOrder.Id |
|
supplier.Id |
|
buyOrder.placed |
|
buyOrder.expectedDeliveryDate |
|
buyOrder.remoteId |
|
Buy Order Lines (Monta > Optiply)
As soon as all lines in Montapacking are 'approved', the order is closed in Optiply and automatically disappears from the booking list in Optiply.
Optiply | Monta |
productId |
|
quantity |
|
subtotalValue | 0 |
buyOrderId |
|
Do not change the reference/PoNumber in Monta.
We will not be able to match our buyOrderID with Montapacking.Reference to get updates or to get any itemDeliveries.
That order will be doubled in Optiply. When syncing buyOrders from Monta, that unknown reference will be seen as a non-existent order in Optiply and it will be created here based on that.
Receipt Lines (Monta > Optiply)
Optiply | Monta |
quantity |
|
ocurred |
|
remoteId |
|