AutohjulLarge-Scale WooCommerce Store

CASE STUDY

Built around a real workflow.

Backend and storefront development for a Swedish tire and rim ecommerce store connected to the Gummigrossen supplier.

OUR CONTRIBUTION

Development responsibilities.

Backend and storefront development covering supplier synchronization, controlled product imports, payment integration and the WordPress shopping experience.

• Supplier synchronization every three hours, processing approximately 60,000 supplier records per run (owner-reported workload).
• Live catalog updates and a separate stock-return processing flow.
• Batch-ID-based imports with supplier payloads persisted before controlled processing.
• Product add/update processing in manageable steps.
• Nexi payment integration.
• A custom WordPress child theme and Elementor-based storefront UI.
• Mobile-friendly development, SEO setup, schema markup scripts, Rank Math configuration and Google Search-related updates.

PROJECT CONTEXT

Commerce with a substantial supplier catalog.

Autohjul serves Swedish customers shopping for tires and rims. Its WooCommerce store connects storefront product discovery with catalog information supplied by Gummigrossen.

DEVELOPMENT

Supplier data, on a regular schedule.

Supplier synchronization runs every three hours. The owner reports approximately 60,000 supplier records processed per run; these figures describe the workload and schedule, not an independently benchmarked performance result.

The confirmed scope includes live catalog updates and a separate stock-return processing flow.

TECHNICAL APPROACH

Persist first. Process in controlled steps.

Each supplier payload is persisted under a batch ID before product processing begins. Product additions and updates then run in manageable steps instead of a single large direct write to the live catalog.

Keeping the source payload associated with its batch makes the synchronization process easier to manage and recover.

DEVELOPMENT

A storefront shaped around the catalog.

Storefront development used a custom WordPress child theme and Elementor-based interfaces. Mobile-friendly development formed part of the confirmed scope, supporting the shopping experience across screen sizes.

DEVELOPMENT

Nexi payment integration.

The project scope includes Nexi payment integration within the WooCommerce store.

DEVELOPMENT

Search foundations and structured information.

SEO work covered setup, schema markup scripts, Rank Math configuration and Google Search-related updates. These are implementation activities; no ranking, traffic or revenue uplift is asserted.

TECHNOLOGY

The project stack.

• WooCommerce
• WordPress
• PHP
• Elementor
• Supplier data integration
• Nexi
• Rank Math
• Schema markup

The supplier payload is first stored under a batch ID. Records are then processed through controlled add/update steps rather than one large direct live write. This makes heavy synchronization more manageable and recoverable.