TECHNOLOGY · SAP COMMERCE CLOUD
Every change goes through a long development cycle. You have to get it right first time.
On SAP Commerce Cloud a list of improvements is worthless unless it's prioritised by what fits in the next release. Judgement matters more than volume.
Let's talk about your project- +15
- years working visibility for large brands
- +200
- projects with our own data behind them
- 48 h
- to reply, at most
Brands that have trusted Laika
Some of these situations may sound familiar
Faceted navigation generates pages with no control
Endless combinations, near-identical content and crawl budget spent on pages nobody searches for.
The catalogue and the site tell different stories
Categories that exist in the catalogue but not in navigation, and the other way round. Each with its own logic.
Performance drops on the pages that matter most
Large listings with many calls and cache layers that don't always help.
Several sites and languages coexist
The same product across different catalogues, with different URLs, languages and availability.
What SEO asks for never makes the release
Usually because it arrives with no estimate, no test case and no statement of the gain. With those, it changes.
The scope
We review catalogue architecture, faceted navigation, URL generation, performance and multi-site configuration, and turn it into work prioritised by release.
We work on the judgement and the spec: what needs to change on SAP Commerce Cloud, in which order and how it gets checked afterwards. Your team or your development partner implements it, and we review that what reaches production is what was agreed.
The areas of work
Four fronts that come up again and again on SAP Commerce Cloud projects. Depending on where your project stands, some weigh more than others.
Catalogue architecture
Make the category structure match how people search, not just how stock is organised.
See the detail
- Map of catalogues, categories and how they surface in navigation
- Detection of orphan or duplicate categories
- Structure proposal based on real demand
- Criteria for adding and retiring categories
Facets and indexing
Decide which combinations deserve to exist and close the rest.
See the detail
- Inventory of facets and the pages they generate
- Indexing rules per combination type
- Canonicals, parameters and pagination
- Tracking of crawled versus useful pages
Performance and cache
Improve response on critical templates without rebuilding the platform.
See the detail
- Measurement by template type on mobile and desktop
- Review of calls, assets and cache layers
- Priorities by revenue impact
- Verification after each release
Specs per release
Get what matters into the next cycle rather than next year.
See the detail
- Tickets with context, acceptance criteria and a test case
- Prioritisation agreed with product and development
- Review in staging
- Record of what shipped and what's pending
Who does it?
A small team with real hours inside SAP Commerce Cloud. MJ leads the strategy and the specialist who reviews your platform is the one who explains it to you.
Why Laika?
Knowing the platform changes the conversation: you stop arguing about whether something is possible and start deciding when it ships.
We've worked on SAP Commerce Cloud projects long enough to know where its real limits are and what a second pass at configuration can solve.
We prioritise by what fits the release
On enterprise platforms the problem isn't knowing what's wrong, it's deciding what changes first.
You always talk to whoever decides
There's no management layer between you and the judgement. MJ leads the strategy and the specialist team executes.
If we're not the right fit, we say so
Even if that means there's no project for us, we'd rather say so before signing.
Frequently asked questions
Do you work with older Hybris versions?
Yes. What changes is how much can be configured versus developed, and that becomes clear in the first review.
Do you work with our integrator?
Yes, that's the norm. We bring the judgement and the spec; they bring the estimate and the development.
How long until we see an effect?
It depends on the release cycle. That's why we prioritise what can ship soon and has a measurable effect.
Tell us about your project
Knowing which version you run, who develops it and what worries you is enough for us to say whether it makes sense to talk.
Shall we talk about your platform?
We look at your project before proposing anything and tell you what can move without fighting the roadmap.
We look at your project before proposing anything. Reply within two working days at most.
Let's talk about your project