IKKS — SFCC feed integrations and OCAPI/SCAPI customisation

The brief

IKKS is a French fashion brand selling across multiple European markets. Fashion retail on Salesforce Commerce Cloud brings a distinct set of backend problems: large, fast-moving catalogues, deep variation structures, and a constant flow of product data out to marketplaces and comparison channels.

What I built

As with the other accounts, the work lived in custom SFRA cartridges — controllers, models and the supporting Business Manager configuration.

The distinguishing feature of this account was feed integration. IKKS syndicates its catalogue to external channels, which means the backend has to produce and maintain product feeds that stay in step with the catalogue in Commerce Cloud.

• Webinterpret — cross-border marketplace listings
• Lengow — feed management and channel distribution

Feed work is deceptively demanding. The mapping is only the first part; the harder part is keeping the feed correct as the catalogue changes underneath it, and making failures visible rather than silent.

OCAPI and SCAPI

This account used both of the platform's API layers. OCAPI is the long-standing REST interface, and SCAPI (Salesforce Commerce API) is its modern successor — faster, built on OAuth 2.0, and the recommended route for new headless work.

Customising these means shaping what external systems can read and write, and doing it without opening more surface than a given integration requires.

Outcome

The integrations ran in production across the period I worked on the account, December 2021 to November 2023.

<!-- TODO(gizem): marketplace count, SKU volume, feed frequency or error-rate improvements would all strengthen this section. Not estimated here. -->

Related work

• Moët & Chandon — cartridges, OCAPI and job workflows
• Facom — Boomi and ShipCompliant integrations
• SFCC cartridge development: the complete guide