Skip to main content
All CollectionsIntegration to ShopifyReference
Shopify Orders - Megaventory Sales Orders
Shopify Orders - Megaventory Sales Orders
Christos Andrianos avatar
Written by Christos Andrianos
Updated over 4 years ago

Here’s how the various order entities are connected in the two applications.

Creation

When a Shopify Order is placed and marked at least as Pending in Shopify, then it will be immediately synchronized to Megaventory. 

When a Megaventory Sales Order is placed in Megaventory, nothing happens in Shopify.

Special case: If a Product specifically has in the Megaventory Custom Order Field 10 the name of a Location, then Shopify Orders are handled differently. If one or more such Products are included in a Shopify Order, then multiple Megaventory Sales Orders are created - one for each different Location present in the Products of the Shopify Order.

Update

When a Shopify Order is updated in Shopify, the status of the relevant Megaventory Sales Order is checked. 

  • If the Megaventory Sales Order is not Pending, then nothing happens in Megaventory. 

  • If the Megaventory Sales Order is Pending, then it is updated. If Products have been removed from the Shopify Order, then these Products are removed from the Megaventory Sales Order too. The other fields (such as line prices, line quantities, document fields) are updated.

Special case: If a Shopify Order has resulted in multiple Megaventory Sales Order, the above check takes place for ALL the relevant Megaventory Sales Orders (ie they need to be all Pending). If a change must happen there are two options:

  • If the Shopify Order is initially associated with a number of Megaventory Sales Orders and after the change, it needs to be associated with less, then the excess Megaventory Sales Orders will be canceled (without changing their content) and the remaining ones will be updated with the correct Products and fields. 

  • If the Shopify Order is initially associated with a number of Megaventory Sales Orders and after the change, it needs to be associated with more, then more Megaventory Sales Orders will be created.

When a Megaventory Sales Order which was initially placed in Shopify is updated in Megaventory, then the following scenarios are available about how Shopify will be updated as a result:

  • If the Megaventory Sales Order fields are updated in Megaventory, then nothing happens in Shopify

  • If the Megaventory Sales Order state is changed to Shipped, then we create a new Fulfillment in Shopify based on the shipped Products

  • If the Megaventory Sales Order state is changed to Cancelled, if all related Megaventory Sales Orders with this Shopify order are Cancelled, then the Shopify Order will be Cancelled

  • If the Megaventory Shipment state is changed to Cancelled, then nothing happens in Shopify

Deletion

When a Shopify Order is deleted in Shopify, the related Megaventory Sales Order(s) is/are cancelled in Megaventory. 

It is not possible to delete Megaventory Sales Orders - see below for cancellations.

Cancellation

When a Shopify Order is canceled in Shopify, then we cancel the related Megaventory Sales Order(s).

When a Megaventory Sales Order is canceled, then, if there are no other related Megaventory Sales Orders to this Shopify Order, the Shopify Order is canceled.

Note: Only Shopify Orders created after the initial synchronization are processed as above - previous ones are ignored.

Manual Order Synchronization

When an Order Synchronization from Shopify to Megaventory fails for any reason, the user has the option to manually retry the failed action. You can do this by clicking the ReSync Order icon under the store's name in the list:

Doing so will toggle the Shopify pop-up, enabling you to enter the Shopify Order ID number in the text box and manually performing an Order Synchronization:


The Shopify Order ID can be found either on your Shopify store or by viewing the Shopify Logs in your Megaventory account. The logs will mention the name of the Shopify Order that has failed to Sync along with its Shopify ID (Entity ID) and the action that caused the error:


Did this answer your question?