Manual order submission
Send eligible Odoo deliveries to AMZPrep automatically instead of recreating fulfillment orders by hand.
Odoo × AMZPrep WMS integration
Odoo AMZPrep Connector
Connect Odoo fulfillment and inventory workflows with an AMZPrep-operated warehouse through the ShipHero API—with automated order handoff, status updates, stock synchronization, and operational traceability.
Built for Odoo Enterprise Edition · Based on ERPixel’s reusable WMS framework · Configuration and implementation assessment required
Product overview
A controlled bridge from Odoo to outsourced fulfillment
Designed for businesses using Odoo with an AMZPrep-operated warehouse through the ShipHero GraphQL API, the connector replaces manual handoffs across fulfillment orders, inventory, shipment status, and tracking. Its AMZPrep-specific API logic runs on ERPixel’s reusable WMS framework for configuration, mappings, scheduling, retries, logging, implementation, and ongoing support.
When the connector helps
Replace fragile fulfillment handoffs
The connector addresses operational gaps between Odoo order management and an external AMZPrep warehouse.
Incomplete warehouse data
Validate addresses, mappings, reservations, warehouse assignment, and order state before transmission.
Disconnected inventory
Apply AMZPrep on-hand quantities to the mapped Odoo warehouse stock location.
Delayed fulfillment status
Poll external order states and reflect processing, fulfillment, and cancellation in the Odoo delivery lifecycle.
Historical-order risk
Use warehouse cut-off protection to avoid accidentally sending migrated or older transactions during go-live.
Opaque integration errors
Inspect request, response, error, status, and chatter context from Odoo rather than treating the API as a black box.
Core capabilities
Built for fulfillment automation and operational control
The verified implementation covers the main workflows required to coordinate Odoo deliveries with AMZPrep fulfillment.
Fulfillment order dispatch
Create AMZPrep orders from eligible Odoo deliveries with recipient, address, SKU, quantity, price, reference, and target warehouse data.
Inventory synchronization
Retrieve warehouse on-hand quantities and update mapped products in the Odoo warehouse stock location.
Product and SKU mapping
Match external SKUs to Odoo Internal References, create or update mappings, and deactivate mappings no longer returned by the WMS.
Warehouse configuration
Synchronize AMZPrep warehouses and explicitly map each participating Odoo warehouse to its external destination.
Fulfillment lifecycle updates
Synchronize processing, fulfilled, and canceled states; fulfilled orders can automatically complete the corresponding Odoo delivery.
Tracking propagation
Write carrier, service, tracking URL, and tracking reference into Odoo when shipment-label data is supplied by AMZPrep/ShipHero.
How it works
A validated path from ERP order to warehouse fulfillment
The integration framework applies mappings, eligibility rules, schedules, status handling, and diagnostics around the AMZPrep API exchange.
Business platform
Odoo ERP
Sales, products, warehouses, reserved stock, outgoing deliveries, and standard tracking fields provide the ERP context.
Integration layer
ERPixel WMS Connector
Validation, mappings, automation controls, retries, cut-off rules, API handling, and logs govern each exchange.
Fulfillment environment
AMZPrep / ShipHero API
The mapped warehouse receives fulfillment orders and returns products, inventory, statuses, locations, and shipment data.
Synchronization is automated and polling-based. Exact schedules, mappings, payload defaults, and warehouse rules are confirmed during implementation.
Supported data flows
What moves between Odoo and AMZPrep
These directions reflect the reviewed implementation. Unverified returns and bin-level stock routing are intentionally excluded.
| Data object | Direction | Operation |
|---|---|---|
| Fulfillment orders | Odoo → AMZPrep | Send validated delivery, recipient, address, SKU, quantity, price, reference, and warehouse data. |
| Products and SKU mappings | AMZPrep → Odoo mapping | Retrieve external products and maintain active mapping records against Odoo Internal References. |
| Warehouses and locations | AMZPrep → Odoo configuration | Synchronize external warehouses plus location names, zones, and pickable/sellable flags as reference data. |
| On-hand inventory | AMZPrep → Odoo | Apply absolute on-hand quantities to mapped products in the corresponding Odoo warehouse. |
| Fulfillment status | AMZPrep → Odoo | Update processing, dispatched/fulfilled, and canceled delivery states. |
| Shipment tracking | AMZPrep → Odoo | Store carrier, service, URL, and tracking reference when the external API supplies shipment-label data. |
Assess your workflow
Will the connector fit your AMZPrep operation?
Share your Odoo environment, warehouses, product identifiers, fulfillment rules, inventory expectations, and AMZPrep API setup. ERPixel will assess configuration and required adaptation.
Reliability and diagnostics
Automation with safeguards and visible recovery paths
The connector includes controls for predictable go-live, transient API conditions, operational exceptions, and ongoing support.
Pre-send validation and cut-off
Check delivery readiness, mappings, required address data, reserved stock, warehouse assignment, and historical-order cut-off before automatic dispatch.
Retries and API handling
Retry failed unsent operations, refresh expired authentication where supported, respect ShipHero rate-limit responses, and paginate large datasets.
Logs and manual controls
Review request, response, and error details; use Odoo chatter traceability and manual actions for testing, support, and exceptions.
Business benefits
Keep ERP and fulfillment aligned without hiding operational detail
The value comes from automating routine exchange while retaining the controls needed to operate and support the integration.
- 01
Reduce manual fulfillment work
Automate eligible order handoff and recurring synchronization instead of maintaining the same process across two systems.
- 02
Prevent avoidable downstream errors
Stop incomplete or ineligible deliveries before they reach the external warehouse.
- 03
Maintain inventory visibility
Bring mapped AMZPrep on-hand quantities into the Odoo warehouse used by the business.
- 04
Close the delivery lifecycle
Use fulfillment and cancellation states to update the corresponding Odoo delivery automatically.
- 05
Support controlled go-live
Protect historical transactions with cut-off rules while retaining deliberate manual override for authorized users.
- 06
Improve supportability
Use structured logs, statuses, responses, tracking fields, and chatter messages to investigate exceptions.
Who it is for
Designed for Odoo businesses using AMZPrep fulfillment
The strongest fit is an operation where Odoo must remain coordinated with an outsourced warehouse across daily order and stock activity.
Ecommerce operations
Connect Odoo order processing with warehouse fulfillment managed in an AMZPrep environment.
Outsourced fulfillment users
Retain ERP visibility after deliveries are handed to an external 3PL workflow.
Multi-warehouse businesses
Route participating Odoo warehouses to explicitly mapped AMZPrep warehouses.
Why ERPixel
A reusable WMS foundation, not isolated API calls
ERPixel combines Odoo delivery expertise with a modular warehouse-integration architecture and verified AMZPrep-specific implementation.
- Official Odoo Partner
End-to-end Odoo implementation, customization, integration, training, and support.
- Reusable WMS framework
Shared mapping, scheduling, retry, logging, status, and fulfillment behavior is separated from the AMZPrep API adapter.
- Operational integration depth
The implementation covers validation, stock, delivery lifecycle, authentication handling, rate limits, diagnostics, and manual exception controls.
Related services
Implementation and support around the connector
Combine the verified integration foundation with the configuration, development, and rollout required by your environment.
Odoo Integration
Design and implement reliable exchanges between Odoo and warehouse or fulfillment platforms.
Odoo Development
Adapt payloads, mappings, workflows, controls, and related Odoo functionality.
Odoo Implementation
Configure Odoo, warehouses, products, stock rules, users, and rollout processes.
Odoo Support
Monitor, troubleshoot, maintain, and continuously improve the integrated environment.
Related products
Explore other ERPixel connectors
See other integrations built around specialized fulfillment and operational environments.
Odoo Mintsoft Connector
Connect Odoo with Mintsoft fulfillment across products, stock, transfers, warehouses, couriers, and sales channels.
Odoo CIRRO Connector
Connect Odoo ERP with CIRRO fulfillment across orders, warehouse routing, sellable inventory, statuses, and tracking.
Odoo CSG Connector
Connect Odoo ERP with CSG fulfillment across shop routing, SKU mappings, usable stock, statuses, and tracking.
Custom connector development
Need Odoo to connect with another warehouse or platform?
ERPixel can design and develop a custom Odoo module or connector around your API, data model, fulfillment rules, automation, and support requirements.
FAQ
Odoo AMZPrep Connector questions
What is the Odoo AMZPrep Connector?
It is an ERPixel WMS integration that connects Odoo ERP fulfillment and inventory workflows with an AMZPrep-operated warehouse environment through the ShipHero GraphQL API.
What data can the connector synchronize?
The verified implementation sends fulfillment orders to AMZPrep and retrieves products for mapping, warehouses, warehouse locations, on-hand inventory, fulfillment statuses, and shipment tracking when the API supplies it.
Does the connector validate orders before sending them?
Yes. It checks delivery state, external WMS ID, warehouse assignment, active product mappings, destination and required address data, stock reservation, and the configured warehouse cut-off.
Can fulfilled AMZPrep orders complete Odoo deliveries?
Yes. When the external status is mapped to fulfilled or dispatched, the framework can automatically validate the corresponding Odoo delivery with safeguards for deliveries already completed.
Is the integration real-time?
The connector uses configurable scheduled background synchronization rather than claiming event-level real-time exchange. The reviewed defaults run order and status processes frequently, while inventory and mapping jobs use separate schedules.
Is the connector plug-and-play?
No generic plug-and-play claim is made. The current implementation is substantial and reusable, but credentials, warehouses, mappings, payload defaults, deployment dependencies, and required adaptations must be reviewed for each environment.
Connect ERP and fulfillment
Need Odoo and AMZPrep to operate as one fulfillment process?
Tell ERPixel about your warehouses, products, order rules, inventory expectations, and support requirements. We will assess the connector fit and implementation path.