When business workflows extend beyond standard retail transactions, basic plug-and-play modules fall short. Standard integrations operate under simple, rigid logic—assuming every order follows the exact same path.
To handle complex B2B scenarios, custom conditional mappings, or multi-warehouse order splitting, businesses often turn to custom software development. However, relying on custom code introduces significant challenges:
-
High Initial & Ongoing Costs: Custom Python modules often require thousands of dollars in upfront development, plus ongoing maintenance fees every time Odoo or ShipStation updates.
-
Protracted Lead Times: Building custom integrations requires writing code, conducting internal testing, and running user acceptance testing (UAT). This process typically delays deployment by weeks or months.
-
Communication & Time Zone Bottlenecks: Custom development teams based overseas can present communication challenges, leading to misaligned specifications and delayed project timelines.
-
Workflow Friction: As operational needs expand and new rules are coded into custom scripts, functions can conflict with core ERP logic or existing code, creating system fragility.
Instead of writing hundreds of lines of custom code, platforms like Connex offer a built-in Rules Engine. This allows you to configure, test, and deploy complex business logic visually without developer intervention.
The Operational Challenge
A business manages B2B orders received via email or phone by entering them directly into Odoo. The orders are sent to ShipStation for fulfillment, and tracking details are passed back to Odoo upon label creation.
While standard connectors map shipping costs uniformly across all shipments, your vendor contracts require specific handling: shipping costs must be zeroed out for specific key accounts (e.g., ABC Battery or XYZ Corp), while standard shipping costs remain mapped for all other customers.
Step-by-Step: Setting Up the Automation in Connex
Step 1: Create the Custom Rule
-
Log into your Connex Dashboard and navigate to the Rules Engine.
-
Click Add New Rule, enter an order number, and click Submit.
-
In the Rule Name field, enter: Map Total Shipping Costs.
-
Under Select Rule, choose Map field, based on a condition.
-
Under Select Action Category, choose Order, search for cost, and select Map Shipping Costs.
Setting the Rule Name, Action Category (Order), and Action Sub Category (Map Shipping Costs) in Connex.
Step 2: Define Your Business Logic & Conditions
-
Under Conditions Match, select One (Any one condition can match / OR logic).
- When you select a field, Connex will show you the billing company for the order. This way, you know the proper field is being mapped.
-
Add your customer conditions:
-
Under Value which needs to be updated, enter 0.
Defining the conditional OR logic for ABC Battery and XYZ Corp and setting the mapped shipping cost value to 0.
Step 3: Test and Validate Instantly
Rather than waiting for a developer to deploy code to a staging environment, you can test your rule immediately using the Connex Order Previewer.
-
Navigate to Rules Engine > Order Previewer.
-
Enter a test order number from your sales channel and click Submit.
-
Select Details on the order result.
-
Review the Rules Running on Order log to verify that the Map Total Shipping Costs rule executed properly and transformed the mapped value to 0.
Verifying rule execution and data transformation inside the Connex Order Previewer.
The Takeaway: Agility Without Code Debt
By leveraging a visual Rules Engine rather than custom scripts, operations teams gain complete control over their logistics workflows:
-
Immediate Deployment: Test and launch new workflow rules in minutes instead of waiting weeks for software updates.
-
Clear Auditability: Use the Order Previewer to inspect data transformations line-by-line before live syncs execute.
-
Zero System Risks: Adjust mapping logic safely in the cloud without modifying underlying Odoo Python code or core database tables.
Ready to Automate Your Odoo–ShipStation Workflow?
Want to see how your non-standard workflows can be automated without custom code?