This article lays out various factors to consider when deciding whether to use our Shopify Connector or implement an API-based integration.
- High-level determination
- Orders & item handling
- Inventory handling
- Technical requirements & support
- Summary - which should you choose?
High-level determination
| Category | Shopify Connector | API-Based Integration |
| Best for | Shopify-first brands with low operational complexity, mostly DTC | Multi-channel, wholesale, ERP-driven, workflow-heavy operations |
| Setup time | Fast (plug & play) | Longer (engineering required) |
| Flexibility | Standardized workflows | Highly configurable |
| Maintenance | Minimal | Requires technical ownership by customer |
| Scalability (volume) | Strong - supports high order volume | Strong - supports high order volume |
| Workflow complexity | Best for straightforward order lifecycles | Designed for complex, multi-state orchestration |
Key distinction:
The Shopify Connector can scale operationally in terms of volume. However, it is designed for standardized workflows. If your business requires complex order manipulation, multi-system orchestration, or heavy customization throughout the order lifecycle, an API-based integration provides significantly more flexibility.
Orders & item handling
| Functionality | Shopify Connector | API-Based Integration |
| Item creation/sync | Auto-created from Shopify | Customer-controlled; can originate from ERP or other systems |
| Order flow | Shopify --> RyderShip only | Any source --> ERP --> RyderShip |
| Support for non-Shopify orders | Limited (Shopify must receive them) | Full (EDI, marketplaces, B2B, POS, ERP-generated). All flow through ERP to RyderShip |
| Metadata / custom fields | Limited support (Rydership does not ingest Shopify tags) | Flexible - use of meta fields to capture any custom data |
| Order manipulation | Limited ability to manipulate orders across multiple lifecycle stages | Greater flexibility across lifecycle stages, with some constraints |
| Orders with VAS (embroidery, gift wrapping, etc) | Limited | Highly configurable |
Inventory handling
| Inventory Behavior | Shopify Connector | API-Based Integration |
| Inventory returned to Shopify | One unified ATS value for a single location | ERP can implement custom logic to control inventory reporting |
Technical requirements & support
| Requirement | Shopify Connector | API-Based Integration |
| Customer technical skill needed | Low | Medium/High - Customer tech team to build/maintain |
Summary - which should you choose?
Choose the Shopify Connector if:
- You operate primarily on Shopify
- You want quick setup with minimal tech lift
You do not require extensive order manipulation after creation
Custom metadata, tags, and advanced field passing are not critical
- You have simple inventory requirements
- Your VAS/custom logic is light or nonexistent
Choose an API-Based Integration if:
- You use an ERP that orchestrates your business (ex: Netsuite)
- You sell through multiple channels (EDI, marketplaces, etc.)
- You require multiple VAS types
- You have technical resources to build + maintain integrations
- Your operational workflows are complex