home.webp
01
Home
services.webp
02
Services
cases_desktop_en.webp
03
Cases
about.webp
04
About Us
careers.webp
05
Careers
blog.webp
06
Blog
contact (1).webp
07
Contact Us
home.webp
01
Home
services.webp
02
Services
cases_desktop_en.webp
03
Cases
about.webp
04
About Us
careers.webp
05
Careers
blog.webp
06
Blog
contact (1).webp
07
Contact Us
Contact Us
Ask for a free consultation now
Case Study

Swissgear

From thousands of individual products to a scalable variant-based architecture.

swissgear-mockup.webp
B2C

A deep catalog transformation, without interrupting the operation.

ABOUT

SwissGear is one of the most recognized brands in backpacks, luggage, and travel accessories in North America, with independent operations in the United States and Canada, and an extensive catalog backed by Acumatica as its central ERP.

CHALLENGE

Each color and variant was managed as an independent product in Shopify, multiplying records, fragmenting the catalog, and tying functionalities, metafields, and integrations with Acumatica to a logic that no longer scaled.

SOLUTION

Massive catalog consolidation into a modern variant-based architecture, with adaptation of functionalities, preservation of the Acumatica integration, and operational continuity simultaneously in the United States and Canada.

A catalog built on an old decision

For a brand like SwissGear, a leader in backpacks, luggage, and travel accessories in the United States and Canada, the catalog is not just an ecommerce component: it is the operation. And that catalog had grown over years on top of a structural decision that, at the time, made sense.

In the store's historic version, each variant of a product — each color, each size, each configuration — was managed as an independent product within Shopify. A backpack available in red, blue, and green was not a single product with three variants: it was three separate products. That logic kept the store operational while the business grew and new lines, colors, and SKUs were added. The catalog grew. The architecture didn't.

When the architecture starts costing more than it delivers

Over time, the store ended up managing 3,385 SKUs on the "one product per variant" logic. What in another context would be an extensive but manageable catalog, in SwissGear was a fragmented catalog, with hundreds of duplicate products representing the same item under different colors and sizes.

The problem was not just volume. The historical structure had shaped everything around it: hundreds of metafields, specific configurations, custom site functionalities, and the Acumatica integration as central ERP. Every technical decision of the past years had been built assuming each product was an independent entity, not a variant. Migrating to a modern architecture was not changing a field or reorganizing the catalog: it was rewriting the foundations of the ecommerce without stopping the business.

Rewriting the foundation with the store live

The decision was to execute the transformation on the same Shopify platform: group individual products into master products with real variants, without migrating to a different stack and without interrupting the operation. The massive consolidation grouped colors, sizes, and configurations under a single product card, reducing the catalog from thousands of products into a clean, scalable structure.


The most complex work was not moving the data: it was adapting everything that depended on the previous logic. Site functionalities were reviewed one by one, deciding case by case what should operate at the product level and what at the variant level. The metafields and the logic accumulated over years were preserved and adapted, avoiding regressions. The Acumatica integration was adjusted to coexist with the new structure without losing functionality — synchronization flows for products, inventory, and operational processes kept running throughout the transition. And all of this was executed in parallel across the United States and Canada, each operation with its own catalogs, inventories, and commercial rules.


On top of that preservation work, there was a critical SEO risk: each of the original 3,385 products had its own indexed URL on Google, and shifting to a variant-based architecture meant most of those URLs would no longer exist. Without a redirect plan, SwissGear would lose much of the organic positioning built over years.


We implemented 301 redirects at the platform level, mapping each legacy URL to its new destination within the variant-based architecture. To prioritize and validate coverage we cross-referenced the previous site's sitemap against Google Search Console data — which URLs drove organic traffic, which queries ranked them, how much they weighed in the site's overall SEO. The catalog transformation went live with no loss of organic positioning and no drop in search traffic.

A foundation ready to grow

Three months after kickoff, the catalog was consolidated: 847 master products grouped the 1,678 variants that previously existed as standalone products, from an original total of 3,385 SKUs. The bilateral operation in the United States and Canada was standardized under the same logic, while maintaining the commercial independence of each market.

But the number that mattered to the business was a different one: during the three months of transformation, the store did not go down, the Acumatica integration kept working, and the internal teams did not have to relearn how to manage the catalog in the middle of the project. The new architecture didn't just simplify day-to-day maintenance — it enabled a foundation on which SwissGear can add new product lines, expand the catalog, and scale operations without rewriting everything again.

Your catalog is your operation. Let's talk.

Click here
driving ecommerce excellencedriving ecommerce excellencedriving ecommerce excellencedriving ecommerce excellence
Copyright 2026 Latech® Company | Todos los derechos reservados