Customize Sana Commerce without breaking the next upgrade.
Sana-certified ProjectThunder customizes Sana Commerce Cloud and 9.x inside the supported framework: themes, add-ons, the SDK, front-end scripting, custom fields, and integrations. The goal is simple. Make it yours, and keep it upgradeable.
Most of what matters, without touching core.
Sana gives you real room to shape the storefront through supported extension points. The trick is knowing which lever to pull, so the result fits your brand and your buyers while the platform keeps updating underneath it. See how we approach builds on Sana Commerce Cloud overall.
Theme & UX
- Custom theme built on Sana's design system: layout, type, color, and component styling that match your brand.
- HTML, CSS, and JavaScript injection from Sana Admin for targeted front-end behavior across the storefront.
- Content and merchandising through the CMS: landing pages, navigation, and product presentation.
- Responsive and accessible work tested on web and mobile, toward WCAG 2.1 AA.
Add-ons & SDK
- Custom add-ons via the Sana Commerce Cloud SDK for capabilities the standard product does not ship.
- Documented extension points rather than core edits, so the add-on stays on Sana's upgrade path.
- Long-term-support SDK cadence so add-on releases land on a predictable schedule.
- Custom checkout steps, storefront logic, and buyer-specific workflows.
Integrations
- Payment: Sana Pay and third-party gateways through supported add-on patterns.
- Tax: provider integrations (for example Vertex or Avalara) without rewriting tax logic in the storefront.
- Search: Sana built-in, or external search wired in for deep B2B catalogs.
- PIM and data: connectors that feed enriched product content into the storefront.
Custom workflows & fields
- Custom fields surfaced from the ERP or Sana onto products, accounts, and orders.
- B2B ordering patterns: reorder, approvals, multi-address, account hierarchy nuances.
- Account portal touches: document attachments, order history views, credit-status visibility.
- Configuration first, code only where configuration genuinely cannot reach.
Why staying inside the framework matters.
Sana Commerce Cloud upgrades automatically about every two weeks. That cadence is a feature, not a nuisance, but only if your customizations are built to ride it. The line between supported customization and risky core change is the whole game.
Supported customization
- Themes, CMS content, and HTML, CSS, and JavaScript injection through Sana Admin.
- Add-ons built against the SDK and documented extension points and APIs.
- Configuration and custom fields rather than forked code.
- Result: the storefront keeps receiving Sana's automatic upgrades and fixes.
Risky core changes
- Editing or forking Sana core code to force a behavior the framework does not expose.
- Customizations Sana cannot upgrade for you, which can pull a project off the automatic-upgrade path.
- Hidden coupling to internals that a later Sana release may change without notice.
- Result: every upgrade becomes a manual, risky merge instead of a quiet background update.
Our rule: configuration first, extension points next, core almost never.
Map the requirement to a lever.
Before we write code, we find whether configuration, a theme change, an injection, or a proper add-on can deliver it. Most things can be done without touching core.
Build on documented APIs.
When code is needed, we use the SDK and Sana's extension points, not internal details that a future release could change. That keeps the work on the upgrade path.
Flag the trade-off honestly.
If a request truly requires a core change, we say so, explain the upgrade cost, and look for a supported alternative before anyone commits to maintaining a fork.
What a customization engagement covers.
Sana Commerce customization, answered.
Will customizations break on Sana upgrades?
They should not, if they are built the right way. Sana Commerce Cloud ships automatic upgrades roughly every two weeks. Work done through supported extension points (themes, HTML and CSS and JavaScript injection, configuration, custom fields, and add-ons that use the documented APIs) rides along with those upgrades. Where projects get into trouble is editing Sana core code, which Sana cannot upgrade for you and which pulls you off the automatic-upgrade path. We keep changes inside the framework so the platform can keep updating underneath them.
Can you customize Sana Commerce Cloud and on-premises 9.x?
Yes, both, though the approach differs. On Sana Commerce Cloud we work through the SDK, the add-on framework, themes, and Sana Admin injections, and we favor extension points so the storefront stays on automatic upgrades. On-premises Sana Commerce 9.x allows deeper code-level customization, but it is a different lifecycle: add-ons are no longer updated for 9.3, so we treat 9.x work as a stable build to maintain rather than a continuously upgrading SaaS. If you are on 9.x and weighing a move to Cloud, we will tell you honestly whether your customizations port cleanly. See our platform comparison if you are also weighing other options.
Can you build a custom add-on?
Yes. We build custom add-ons with the Sana Commerce Cloud SDK for capabilities the standard product does not cover: a bespoke payment or tax provider, a connector to a PIM or search service, a custom checkout step, or storefront logic specific to how your buyers order. We build against documented extension points and APIs rather than patching core, run the add-on through Sana's long-term-support SDK cadence, and test it against staging before it reaches production.
Do you work with our ERP partner?
Yes, and we do it often. Many Sana projects involve a separate ERP or Sana implementation partner who owns the SAP or Microsoft Dynamics side. We slot in as the web, design, and development team: we handle the storefront, theme, add-ons, and front-end integrations, and we coordinate with your ERP partner on data contracts and field mapping. We are a Sana-certified web and development agency, not an ERP reseller, so we are comfortable sharing the work rather than owning every layer. Learn more about working with our Sana Commerce agency team.
Have a customization in mind?
Tell us what you need the storefront to do. We will tell you whether it lives in a theme, an injection, an add-on, or (rarely) something deeper, and we will keep it upgrade-safe.
877.609.9029