{"id":24506,"date":"2026-02-11T13:36:01","date_gmt":"2026-02-11T13:36:01","guid":{"rendered":"https:\/\/what.digital\/?p=24506"},"modified":"2026-04-03T08:40:06","modified_gmt":"2026-04-03T08:40:06","slug":"erp-connector-store-merge-rokker","status":"publish","type":"post","link":"https:\/\/what.digital\/erp-connector-store-merge-rokker\/","title":{"rendered":"Dataforce (Palos) ERP Connector Redesign & Shopify Store Merge: Rokker Case"},"content":{"rendered":"\n

The Rokker Company AG needed a stable ERP-Shopify connection, but their Dataforce (Palos) integration kept failing. Orders were fully manual, price calculations created chaos, and the whole setup was costing them sales.<\/p>\n\n\n\n

We rebuilt the connector from scratch, merged their stores, and cut monthly costs by CHF 2000. Here’s what actually happened.<\/p>\n\n\n\n

The Connector Went Live \u2013 But Not Without Pain<\/strong><\/h2>\n\n\n\n

Mid-December 2025, we launched the new ERP connector. It replaced an outdated FTP-based system that relied on custom ColdFusion code and a Shopify API version from 2020.<\/p>\n\n\n\n

The old setup? Unreliable at best. Stock levels were wrong, order transmission broke regularly, and nobody could trace where things went sideways.<\/p>\n\n\n\n

The new connector stabilized things \u2013 but not immediately. We spent the first two weeks of 2026 fixing edge cases and syncing issues. By week 2, it was solid.<\/p>\n\n\n\n

The lesson<\/strong>: Even when you rebuild something properly, expect a transition period. FTP dependencies and legacy APIs don’t just disappear \u2013 they hide problems you only discover when real orders start flowing.<\/p>\n\n\n\n

Price Calculation Differences Nearly Killed Automation<\/strong><\/h2>\n\n\n\n

Here’s a fun one: Shopify calculates B2C prices including VAT per line item. Dataforce calculates B2B prices excluding VAT.<\/p>\n\n\n\n

Sounds manageable, right? Wrong.<\/p>\n\n\n\n

Rounding differences meant totals didn’t match between systems. Dataforce couldn’t generate invoices automatically because the numbers were off \u2013 sometimes by cents, but off enough to block the entire process.<\/p>\n\n\n\n

We had to align the calculation logic on both sides, add missing VAT rates in the ERP, and fix incomplete shipping cost data. Only then could orders flow through without manual intervention.<\/p>\n\n\n\n

What we’d tell anyone doing ERP integration<\/strong>: Test your price calculation logic with real-world orders before<\/em> you go live. B2C\/B2B mismatches, rounding rules, and tax handling will break things in ways mockups never reveal.<\/p>\n\n\n\n

Store Merge Freed Up Budget and Simplified Operations<\/strong><\/h2>\n\n\n\n

The Rokker Company AG ran multiple Shopify stores in parallel. Different pricing, different apps, overlapping functionality \u2013 and monthly costs piling up.<\/p>\n\n\n\n

We consolidated down to a cleaner setup, harmonized pricing across markets, and cut unnecessary app subscriptions. That alone saved around CHF 2000 per month.<\/p>\n\n\n\n

The merge itself finished by end of December 2025. One less store to manage means fewer errors, less admin overhead, and clearer data.<\/p>\n\n\n\n

The trade-off<\/strong>: Merging stores sounds simple until you hit payment providers, tax rules, and marketing tracking. Which brings us to…<\/p>\n\n\n\n

Subdirectories Got Blocked \u2013 by an External Agency<\/strong><\/h2>\n\n\n\n

We designed and prepared a proper Shopify Markets structure with subdirectories (ch-de, de-de, at-de, etc.). Clean URLs, better SEO, proper market segmentation.<\/p>\n\n\n\n

It was ready to launch, but a delay came up. Why? The performance marketing agency was not informed at the right time. Instructions were passed to us by proxy, generating some confusion and delay until it has been properly resolved.<\/p>\n\n\n\n

The takeaway<\/strong>: If you’re merging stores or restructuring markets, loop in everyone<\/em> who touches URLs, tracking, or ad campaigns. Marketing agencies need lead time \u2013 and surprises tank launch schedules.<\/p>\n\n\n\n

What’s Still Open (and Why It Matters)<\/strong><\/h2>\n\n\n\n

The following procedure remains unresolved:<\/p>\n\n\n\n

Internal Dataforce mapping<\/strong> for some customer-specific quirks can only be solved three ways: extend the orders API, change Rokker’s internal process, or create custom mapping inside Dataforce itself.<\/p>\n\n\n\n

We’ve laid out the options. The decision sits with the client.<\/p>\n\n\n\n

Why this matters for you<\/strong>: Even when the technical work is done, organizational alignment determines whether you actually use<\/em> what you built. Budget time for internal coordination \u2013 it’s rarely quick.<\/p>\n\n\n\n

What Actually Worked<\/strong><\/h2>\n\n\n\n

Despite the friction, the project delivered:<\/p>\n\n\n\n