How we modernized Artika's marketplace and EDI integrations

 

Artika is a Montreal-based decorative lighting and home décor brand selling across Amazon, Walmart, Costco, Best Buy, Houzz, and its own Shopify storefront. As part of a broader digital transformation, the company was migrating from Microsoft Dynamics NAV to NetSuite on a fixed delivery timeline. The integration layer connecting its marketplaces, fulfillment partners, and EDI trading partners to the new ERP had fallen behind schedule.

This case study examines how Twenty20 Systems took ownership of the integration architecture, redesigned it for scale, and delivered the core integrations in a fraction of the original estimate. Original timeline: 56 weeks. Actual delivery: 25.

 

The Scenario at Engagement: A Stalled Marketplace Integration Programme

The integration effort had already begun with another platform before Twenty20 was engaged. The project was falling behind, and the existing setup was struggling to meet enterprise requirements. Artika initially brought Twenty20 in to assess the situation, then transitioned the engagement into full ownership of the integration architecture, development, and delivery.

The constraints framing the engagement were significant:

• The NetSuite ERP itself was being configured in parallel, with fields and structures evolving alongside the integration work
• The marketplaces did not offer sandbox environments, requiring careful testing strategies against live systems
• Multiple systems and vendors required coordination across regions and time zones
• The delivery timeline was fixed, with no room for slippage

 

The Twenty20 Approach: Reusable Integration Architecture for Enterprise Scale

Building seven marketplace integrations as seven independent projects was incompatible with the timeline and with long-term maintainability. Twenty20's recommendation was a reusable integration architecture that captured common flows once and treated marketplace-specific behaviour as configuration. The benefits were twofold: faster initial delivery, and lower cost to onboard the next marketplace or trading partner.

The same six categories of data flow into NetSuite from every marketplace: orders, fulfillment updates, inventory, cancellations, refunds, and pricing. What varies between channels is the API contract, the authentication model, and a series of regional edge cases. Twenty20 standardised the six flows once into a shared recipe template, with marketplace-specific variations layered on top rather than embedded inside.

For the Amazon integration, Twenty20 engineered a custom Amazon Seller Central connector to handle authentication and to avoid the HTTP connection timeout issues a generic adapter encounters. The connector also manages OAuth token refresh and supports both the US and Canadian marketplaces. Runtime configuration (polling timestamps, feed trackers, error codes, province and territory mappings) was externalised into lookup tables, keeping operational logic separate from the recipes themselves.

Error handling was treated as part of the architecture rather than a final-stage addition. Every recipe runs inside try-catch blocks with configurable retry logic, supported by a global error notification function that captures the full operational context of any failure: error code, message, stack trace, and parent job ID. Job reports include custom columns for polling timestamps and integration status, enabling rapid audit and replay.

Throughout the build, Twenty20 coordinated closely with third-party providers, including EDI partners such as Orderful, to ensure clean data exchange for retail trading relationships including Walmart, Costco, and BestBuy. The architecture itself was implemented on Workato as the iPaaS layer.

 

 

Outcomes: A Compressed Timeline and a Scalable Foundation

Twenty20's work delivered the following across the engagement:

• End-to-end order-to-cash integrations across 7+ marketplaces
• Centralised synchronisation of orders, fulfillment, inventory, and returns into NetSuite
• A scalable integration architecture built on reusable recipes
• Operational coverage across the United States and Canada
• 3PL connectivity for fulfillment coordination and shipment visibility
• Real-time error monitoring and alerting, with diagnostics designed for rapid triage
• Business process refinement aligned with marketplace and ERP workflows
• Structured cutover support during the Microsoft Dynamics NAV to NetSuite migration
• Post-go-live hypercare to stabilise operations through the initial rollout phase

By standardising integration patterns and prioritising scalability, the delivery timeline was compressed from an estimated 56 weeks to 25. The core integrations are live and supporting day-to-day marketplace operations, with a stable foundation in place for further expansion.

 

Lessons Learned from a Compressed-Timeline Enterprise Integration

Several principles emerged from the engagement that apply broadly to enterprise iPaaS implementations operating under similar conditions.

Structured cadence enables work against a moving target. With NetSuite being configured in parallel, field mappings and business logic were subject to ongoing change. Twenty20 maintained daily synchronisation with the NetSuite implementation team, a live aging report on open items, and bi-weekly steering reviews, which kept ERP and integration changes coordinated rather than colliding.

Layered testing strategies replace missing sandbox environments. In the absence of test environments from Amazon, Walmart, BestBuy, and Costco, Twenty20 combined seller testing tools where available, specially flagged test orders, controlled testing windows during low-traffic periods, and incremental rollout patterns with rapid rollback paths. The result was thorough validation without disruption to live commerce.

Configuration-driven design absorbs multi-geography complexity. Operating across multiple regions introduces variations in tax rules, shipping logic, and EDI compliance requirements. Configurable integration logic, supported by lookup tables and externalised environment variables, accommodates these differences without forcing maintainability compromises.

Central coordination reduces integration risk in multi-vendor programmes. With Artika's internal team, the NetSuite implementation team, marketplace technical contacts, SFTP trading partner contacts, and 3PL providers all in motion concurrently, Twenty20 served as the single coordination point preventing dependencies from falling between organisational boundaries.

 

Talk to Us About Your EDI and Integration Needs

Enterprise ERP migrations frequently encounter difficulty in the integration layer rather than in the ERP itself. Fragmented integrations, mid-flight ERP migrations, and marketplace onboarding tend to surface the same categories of risk: scalability gaps, EDI compliance exposure, and timeline pressure compounding into delivery slippage.

If your organisation is navigating any of these challenges, get in touch with Twenty20 Systems to discuss how our EDI and integration capabilities can support your roadmap. To explore the full scope of what we deliver across EDI implementation, marketplace connectivity, and trading partner onboarding, download our EDI services overview for a detailed look at our offerings.