This mistake can kill your project before you even start

This mistake can kill your project before you even start

This mistake can kill your project before you even start

  • Jonatan Jumbert

  • 2 minute read

Some mistakes?
You don’t see them until it’s too late.

This one?
It happens all the time.

So let’s talk about it.

Because if you don’t pay attention, you’ll suffer later.

Unlock SFCC Pro Tips!

Imagine what you’re missing in our other guides! Stay ahead of the competition, get exclusive pro tips, and master Salesforce Commerce Cloud like never before.

👉 Subscribe NOW and never struggle with SFCC again!

𝗧𝗵𝗲 𝘀𝗲𝘁𝘂𝗽
New project.
Discovery phase? ✅ Done.
Integrations? ✅ Clear.
Data model? ✅ Understood.
Migration plan? ✅ In place.

𝙉𝙤𝙬, 𝙞𝙩'𝙨 𝙩𝙞𝙢𝙚 𝙩𝙤 𝙙𝙚𝙨𝙞𝙜𝙣.

The design team—whether in-house or an external agency—gets to work.
They take all the project requirements and turn them into something visual.

𝘈 𝘣𝘦𝘢𝘶𝘵𝘪𝘧𝘶𝘭, 𝘦𝘯𝘨𝘢𝘨𝘪𝘯𝘨, 𝘩𝘪𝘨𝘩-𝘤𝘰𝘯𝘷𝘦𝘳𝘵𝘪𝘯𝘨 𝘸𝘦𝘣𝘴𝘪𝘵𝘦.

So far, so good, right?

𝗪𝗿𝗼𝗻𝗴.

Here’s the problem
Design teams are creative.
𝗕𝘂𝘁 𝘁𝗵𝗲𝘆 𝗱𝗼𝗻’𝘁 𝗸𝗻𝗼𝘄 𝗦𝗮𝗹𝗲𝘀𝗳𝗼𝗿𝗰𝗲 𝗖𝗼𝗺𝗺𝗲𝗿𝗰𝗲 𝗖𝗹𝗼𝘂𝗱.

And who does?
You.
Me.
The development team.

And if we don’t guide them?

They’ll create something amazing on paper… but 𝗮 𝗻𝗶𝗴𝗵𝘁𝗺𝗮𝗿𝗲 𝘁𝗼 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁.

Real example: SFRA

Let’s say your project is using SFRA.
One of SFRA’s biggest strengths?

It comes with pre-built templates.
Homepage ✅
PLP (Product Listing Page) ✅
Filter system ✅
Multi-step checkout ✅
Login & registration pages ✅

Everything is there.

Structured.
Optimized.

But if the design team doesn’t know this?

They might decide:
💡 "𝗟𝗲𝘁’𝘀 𝗱𝗼 𝗮 𝗼𝗻𝗲-𝘀𝘁𝗲𝗽 𝗰𝗵𝗲𝗰𝗸𝗼𝘂𝘁 𝗶𝗻𝘀𝘁𝗲𝗮𝗱!"

Sounds great.

Except…
SFRA uses a multi-step checkout.

𝗪𝗵𝗶𝗰𝗵 𝗺𝗲𝗮𝗻𝘀?
The checkout module you already have becomes useless.
Now you have to build a custom checkout from scratch.

Rewrite the logic.
Fix compatibility issues.
Test endlessly.

💀 𝗪𝗵𝗮𝘁 𝘄𝗮𝘀 𝗮 𝟭𝟮-𝗺𝗼𝗻𝘁𝗵 𝗽𝗿𝗼𝗷𝗲𝗰𝘁 𝘀𝘂𝗱𝗱𝗲𝗻𝗹𝘆 𝗯𝗲𝗰𝗼𝗺𝗲𝘀 𝟭𝟱, 𝗺𝗮𝘆𝗯𝗲 𝟭𝟴 𝗺𝗼𝗻𝘁𝗵𝘀.

...Why?

Because no one stopped the design team before they went too far.

𝗧𝗵𝗲 𝘀𝗼𝗹𝘂𝘁𝗶𝗼𝗻

You must guide the design team.
Show them how SFRA works.
Share the SFRA demo site so they can explore.

Help them understand what can be customized easily and what can't.

Be in constant communication to avoid surprises.
🚨 Because if you don’t, you’ll regret it later.

Because knowing what to do isn’t enough.
You also need to know what to avoid. 🚀


Recommended Courses