Migrate from Shipedge to Odoo ERP

Shipedge Orders map to Odoo sale.order records with order lines, partner shipping and invoicing addresses, and carrier service-level preserved. Shipedge's fulfillment status (pending, shipped, cancelled) maps to Odoo's picking_id state and order procurement workflow. We extract order source channel (Shopify, Amazon, Walmart) as a custom char field x_source_channel on the sale.order for reporting.

Shipedge shipment records map to Odoo stock.picking with carrier, service level, tracking number, weight, and dimensions preserved. Tracking URLs migrate as Char fields linked to the picking. If Shipedge stores multiple shipments per order (split shipments), each generates a separate stock.picking in Odoo.

Shipedge Products carry SKU-level details, variant attributes (size, color), supplier links, and barcodes. We map these to Odoo product.template (shared attributes) with product.product variants per SKU combination. Shipedge's barcode field maps to product.product barcodes. Supplier links map to product.supplierinfo records for purchase pricing and lead times.

Shipedge inventory is warehouse-site-specific with location-aware quantities, lot numbers, and bin assignments. We map each Shipedge warehouse to an Odoo stock.location (type warehouse), each Shipedge bin to a child stock.location (type internal), and inventory quantities to stock.quant records linked to those locations. Lot and serial numbers migrate as stock.productionlot records and linked to quants.

Shipedge's multi-warehouse configuration maps to Odoo stock.warehouse records, each with its own picking types (incoming, outgoing, internal). We preserve warehouse address, operating hours, and carrier shipping accounts as Odoo warehouse configuration parameters. If Shipedge has cross-docking or drop-shipping rules, we flag these for manual reconstruction as Odoo warehouse routes.

Shipedge Customer records map to Odoo res.partner with type customer. Name, email, billing address, and shipping address migrate directly. Order history associations export as a custom related field or many2many linking to sale.order records. Custom fields on Shipedge customers require manual field creation in Odoo and mapping during import.

Shipedge Suppliers map to Odoo res.partner records with supplier_rank set to 1. Contact details, lead times, and SKU associations migrate as product.supplierinfo records. We flag any custom fields on Supplier records for manual Odoo field creation and mapping. Purchase order history from Shipedge maps to Odoo purchase.order records if the customer activates the Purchase module.

Shipedge Return Authorizations, return reasons, and disposition codes map to Odoo return picking records. We translate Shipedge disposition codes (restock, dispose, repair) to Odoo stock.move scrap or repair records depending on disposition type. Return partner information maps to res.partner. We flag disposition mapping decisions during scoping because Odoo's return logic is module-specific (Stock vs Repair vs RMA apps).

Shipedge Kit configurations (which SKUs compose a kit, on-the-fly vs pre-built) map to Odoo mrp.bom records with type phantom for on-the-fly kit deduction or normal for pre-built assemblies. We export kit structure and component links but note that kit representation differs significantly: Odoo BoM uses product templates and routing operations that must be configured in the Manufacturing module. Manual BoM reconstruction is required post-import.

Shipedge v11+ Batch Fulfillment View records contain batch number, order count, SKU count, and units. Batch number maps to Odoo stock.productionlot (for lot tracking) linked to stock.quant. Batch metadata (order count, ship method) does not have a direct Odoo analog and is preserved as a note field on the production lot or as a custom Char field.

Shipedge Order Rules define automated warehouse selection, carrier assignment, and split-order routing. These are Shipedge-specific workflow configurations with no Odoo direct equivalent. We export all Order Rules as a written inventory during discovery, identifying the rule name, trigger conditions, and routing actions so the customer's Odoo admin can rebuild them as stock.routes, procurement rules, or delivery.carrier rules. This is a manual rebuild exercise estimated at 1-3 days depending on rule complexity.

Shipedge channel integrations (Shopify, Amazon, Walmart, Magento) store OAuth tokens and API credentials inside its integration module. These are platform-bound secrets that cannot be exported. We document which channels are active, their configuration parameters, and their order-pull and inventory-sync settings. After migration, every channel must be re-authorized in Odoo's eCommerce or Point of Sale modules. We provide a reconnection checklist to accelerate re-authorization.