Send Odoo Order and Customer Details to Shopify

The trigger checks your Odoo system every hour for newly created sales orders. When new orders are detected, it captures the basic order information and passes it to the next step for detailed retrieval. You can adjust the hourly schedule if you need more or less frequent syncing based on your order volume.

The step retrieves the full sales order from Odoo using the order ID from the trigger. This includes the order total, currency, tax calculations, customer ID, and all other order-level data. The complete order details get used later when creating the Shopify order with accurate financial information.

The step retrieves the customer (partner) record from Odoo using the customer ID from the order. This includes the customer's complete name, email, phone, street address, city, state/province, postal code, country, and any notes. These details get used to either create a new Shopify customer or update an existing one, and to populate billing and shipping addresses on the Shopify order.

The step queries Odoo for all order lines associated with this sales order, searching by the order name. Each order line includes the product ID, quantity, unit price, and product name. These lines get processed in the next loop to fetch product details and match them to Shopify variants.

The loop iterates through all order lines retrieved in Step 4, processing one product at a time. For each line item, the loop passes the product ID to the next step to fetch full product variant details including the SKU that's critical for matching to Shopify.

The step retrieves the full product variant from Odoo using the product ID from the current order line being processed. Most importantly, it gets the "default_code" field which is Odoo's SKU, along with the product name and other details. This SKU gets used in the custom code step to find the matching Shopify product variant.

The Loop End step pairs with the Loop from Step 5 and uses a special "return: map" feature to collect all the product variant records retrieved during the loop iterations. Instead of just closing the loop, it creates an array called "items" containing all the Odoo product variants, which gets passed to the custom code for SKU matching.

The custom code performs several critical functions:

1. Extract customer address details: Parses the state/province from Odoo's formatted state field and handles the street2 (address line 2) field
2. Add SKUs to order lines: Matches each order line to its product variant to include the SKU (default_code)
3. Query Shopify for matching variants: For each SKU, makes a GraphQL query to Shopify to find the corresponding product variant
4. Match and enrich order lines: Combines Odoo order line data with Shopify variant IDs, creating a complete dataset with both systems' identifiers

The code outputs:

• customer.state: Extracted state/province for addresses
• customer.street2: Second address line
• order_lines[]: Array of order lines with Odoo details plus Shopify product and variant IDs

This matching process ensures that when the Shopify order is created, it references the correct Shopify products even though the order originated in Odoo.

The step queries Shopify's customer database filtering by the email address from the Odoo customer record. It limits the search to return just 1 customer since emails should be unique. If a matching customer exists, the workflow updates their information; if no customer exists, the workflow creates a new customer record.

The step checks if the customer ID from the search "is empty." If no customer was found, the workflow continues down this path to create a new customer record with the Odoo customer's information. If a customer exists, this path stops and the workflow routes to the update path instead.

The step creates a new Shopify customer using data from Odoo. It populates:

• Email from Odoo customer
• First and last name (split from Odoo's complete_name field)
• Phone number
• Customer notes/comments
• A default address with street, street2, city, state, country, postal code

The custom code output provides the formatted state and street2 fields that Shopify requires.

The step checks if the customer ID from the search "is not empty." If a customer was found, the workflow continues down this path to update their record with any changes from Odoo (like a new address or phone number). If no customer exists, this path stops since the create path already handled it.

The step updates the existing Shopify customer using the customer ID from the search. It updates the same fields as the create step—email, name, phone, notes, and addresses—with current data from Odoo. This ensures the Shopify customer record reflects any changes made in Odoo since they were last synced.

The step uses a always-true condition to ensure this path runs for every order. After either creating or updating the customer in the previous paths, the workflow needs a single path to create the order. This design pattern allows the workflow to handle customer logic separately from order creation while ensuring every order gets created.

The step creates a new Shopify order with comprehensive details:

• Order basics: Currency, email, order name from Odoo
• Line items: Each product with variant ID (from custom code matching), quantity, title, SKU, and price
• Customer info: Email, first and last name
• Billing address: Complete address with street, street2, city, state, country, postal code
• Shipping address: Same format as billing address
• Tax lines: Tax amount from Odoo order totals
• Inventory behavior: Set to "bypass" so the order creation doesn't affect Shopify inventory levels

The order uses all the data gathered and transformed in previous steps—matched product variants from custom code, customer details from Odoo, and formatted addresses. The inventory_behaviour is set to "bypass" because Odoo is managing the actual inventory, not Shopify.