What surprised me migrating BMWParts.bg to Shopify

Practical lessons from migrating BMWParts.bg to Shopify: a courier integration, a catalogue with 114 BMW generations, payments and data checks.

The home page of bmwparts.bg: the headline “The right parts. For your BMW.” and a picker for the BMW series and generation.Enlarge

I migrated BMWParts.bg from CloudCart to Shopify. The scope covered 180 products and 408 prepared old-to-new URL mappings. These are scope figures, not a measurement of traffic, rankings or sales.

The courier app

The project used the courier app for collection-point selection. The implementation needed adjustments to its presentation and behaviour on mobile.

I adjusted its appearance with custom CSS. This was an observation from the BMWParts.bg integration, rather than a rating of the app across all stores.

If you are choosing a delivery app, do not stop at "does it work". Run a test order, go through the whole office selection on a phone, and only then decide whether you want someone else's code on your checkout.

Payments

Check Shopify Payments availability and the requirements for the business, its verification and bank account in the official Shopify documentation. Availability in a country does not establish that an individual store has been approved.

Payout timing depends on the account, its payout schedule and bank processing. Check the current terms before planning cash flow.

The menu and the models

In the previous version of BMWParts.bg, navigation was organised as a list of BMW series. During the migration I chose a two-step menu: first the series, then the generation. This was a project decision based on the catalogue and how customers search for parts, rather than a limitation attributed to the previous platform.

The open menu on bmwparts.bg: BMW series, and under each series separate generations, for example E81, E82, E87, E88, F20, F21, F40 and F70 for the 1 Series.Enlarge

The result is 114 generations in 10 model families. The collections are automatic. Products carry tags like bmw-model-e60, and each generation is a collection with the rule "tag contains bmw-model-e60". Once a product gets the tag, it joins the collection by itself.

The product page also has a "BMW models" block listing the models the part fits. Each one links to that generation's collection, so one click shows only parts for that model. That was quite custom work, and I really liked how it turned out.

A product page on bmwparts.bg with a "BMW models" block listing the generations the part fits (E60, E61, E63, E64, E65, E66, E81, E82) and a link "More BMW models (11)".Enlarge

I do not add compatibility on a guess. When the source data does not support a product-to-generation link, I leave it unassigned. The buyer still needs to check the VIN and equipment before ordering.

What I check before migration

  1. I crawl the old site with Screaming Frog before touching anything. URLs, products, categories, the blog. After the migration the old site is gone, and the redirect map is built from this list. Without it you are guessing.
  2. I check the export options available in the specific store, the data they include, and any limits or additional terms of its plan. These need to be established before the migration date.
  3. I check where the compatibility data comes from. If it is not in the export, I do not invent it.
  4. I test redirects exactly as they are written. On my own site I saw a check that tidied each address before comparing it let 20 addresses through that Google was already listing as redirected. If a link in a page has no trailing slash and the rule has one, you only see it by testing exactly that.

None of this is a promise of rankings or traffic. I do it before changing the platform, not after.

Official documentation:

Shopify Payments requirements

CloudCart: export of orders, ordered products and invoices

Continue exploring