You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 20, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 20, 2026. It is now read-only.
Right now, the code base is strictly coupled with data hooks providers. We need to enable the use of different providers interchangeably.
We’re discussing steps forward with @lfades to add different data sources to Next.js Commerce and make it super easy to switch data providers and even aggregate them.
Goals of Commerce
Next.js Commerce should have a completely data agnostic UI
Aware of schema: should ship with the right data schemas and types.
All providers should return the right data types and schemas to blend correctly with Next.js Commerce.
@framework will be the alias utilized in commerce and it will map to the ecommerce provider of preference- e.g BigCommerce, Shopify, Swell. All providers should expose the same standardized functions. Note that the same applies for recipes using a CMS + an ecommerce provider.
There is a framework folder in the root folder that will contain multiple ecommerce providers.
Additionally, we need to ensure feature parity (not all providers have e.g. wishlist) we will also have to build a feature API to disable/enable features in the UI.
Reacted by Masahiro Saito, Martin Smit, Thiago Morales, Adam Grohs, Simon Renault, Andrew Scofield, Felix Tellmann, Ludvig, Alex , Dennis Rehbehn and 31 more
Reacted by James Singleton, Jon Wu, Hervé Hubert, Fredrik Pettersen, Miguel Peixe Aldeias, Agusti F., robbieaverill, ralphilius, Feek, Michael Bromley and 28 more
Reacted by fravelgue, Emanuele Buccelli, Masahiro Saito, Alexandros Dorodoulis, Yony and Убо
Another thought: Could we package the front-end somehow so existing Commerce users can get bug fixes pushed? This is tough because then they can't really customize their forked version.
@leerob my 2 cents: I think it is far preferable to package the project for distribution via npm. Relying on forking becomes utterly painful when big changes are made to the fork and upstream too, and then the user is left trying to merge and get it right - not a nice experience!
Of course then there is the problem that an npm package is not a storefront. So there still needs to be some "scaffold" which consumes the npm package, and this scaffold part cannot be easily versioned. But if well-designed this can be kept to a minimal issue, since it is the core components in the npm package which will be changed more often.
For example, how Angular does it with their CLI is pretty nice: the core libs are in npm packages, but some parts like your project package.json, angular.json, tsconfig.json and other parts are local to your repo. When upgrading they use an AST-based tool (schematics) to automatically apply codemods to your repo to keep it compatible with the latest package version. This may be overkill for this project, but I just give it as an example of what can be done.
Reacted by maartenjongerius, Martin Smit and Ishimoto Koji
I'm also keen to build in support for other eCommerce APIs. Two things are stopping me right now: 1) there's no license on this repository (edit: there is now:#95), 2) there's no checkout. Having an external checkout is pretty jarring from a UX perspective, and kind of antiquated in my opinion. The value of jamstack is having everything be headless and API driven in order to create efficient, optimised, and unique user experiences in the commerce space, which 50% of this project is not at time of writing.
I imagine adding a checkout here would also involve building some additional UI components for it, and would involve coordination with the maintainers of this repository to ensure we get what we want. In the meantime, BigCommerce/Shopify/other eCommerce providers that have externally hosted checkouts seem to be the only option.
I'm also keen to build in support for other eCommerce APIs. Two things are stopping me right now: 1) there's no license on this repository, 2) there's no checkout. Having an external checkout is pretty jarring from a UX perspective, and kind of antiquated in my opinion. The value of jamstack is having everything be headless and API driven in order to create efficient, optimised, and unique user experiences in the commerce space, which 50% of this project is not.
I imagine adding a checkout here would also involve building some additional UI components for it, and would involve coordination with the maintainers of this repository to ensure we get what we want. In the meantime, BigCommerce/Shopify/other eCommerce providers that have externally hosted checkouts seem to be the only option.
Very interested in this as well, I imagine an abstraction layer and a set of capability flags would make it easier to support other commerce backends without forcing everyone to implement the same common subset of features.
Edit: I should make it clear that one of those features is a checkout API as opposed to a hosted checkout view.
@okbel
Hi,
Can you please share your branch you working on this issue?
It's great if I can join to help for improve the implementation on it, because this is the most important feature.
Reacted by Lars Buur, Mokhtar, amesas and Ján Bočínec
Activity
leerob commentedon Oct 28, 2020
Another thought: Could we package the front-end somehow so existing Commerce users can get bug fixes pushed? This is tough because then they can't really customize their forked version.
https://twitter.com/PrevostClemToun/status/1321387261511028743
michaelbromley commentedon Oct 28, 2020
@leerob my 2 cents: I think it is far preferable to package the project for distribution via npm. Relying on forking becomes utterly painful when big changes are made to the fork and upstream too, and then the user is left trying to merge and get it right - not a nice experience!
Of course then there is the problem that an npm package is not a storefront. So there still needs to be some "scaffold" which consumes the npm package, and this scaffold part cannot be easily versioned. But if well-designed this can be kept to a minimal issue, since it is the core components in the npm package which will be changed more often.
For example, how Angular does it with their CLI is pretty nice: the core libs are in npm packages, but some parts like your project package.json, angular.json, tsconfig.json and other parts are local to your repo. When upgrading they use an AST-based tool (schematics) to automatically apply codemods to your repo to keep it compatible with the latest package version. This may be overkill for this project, but I just give it as an example of what can be done.
hoektoe commentedon Oct 28, 2020
Would be great to support shopify also like Gatsby but better since it's nextjs
Clausinho commentedon Oct 28, 2020
I've seen a lot of support for shopify, but are there any plans for woocommerce or is it simply not economically viable?
jerrylopez commentedon Oct 29, 2020
I would love to work on a Magento provider. Is there other conversations happening outside of this issue regarding external providers?
robbieaverill commentedon Oct 29, 2020
I'm also keen to build in support for other eCommerce APIs. Two things are stopping me right now: 1)
there's no license on this repository(edit: there is now: #95), 2) there's no checkout. Having an external checkout is pretty jarring from a UX perspective, and kind of antiquated in my opinion. The value of jamstack is having everything be headless and API driven in order to create efficient, optimised, and unique user experiences in the commerce space, which 50% of this project is not at time of writing.I imagine adding a checkout here would also involve building some additional UI components for it, and would involve coordination with the maintainers of this repository to ensure we get what we want. In the meantime, BigCommerce/Shopify/other eCommerce providers that have externally hosted checkouts seem to be the only option.
agustif commentedon Oct 30, 2020
Stripe Checkout is a nice hosted solution, there's already examples with next https://github.com/stripe-samples/nextjs-typescript-react-stripe-js
martinbavio commentedon Nov 4, 2020
@robbieaverill started a RFC in order to talk about a fully custom checkout: #64
patrys commentedon Nov 5, 2020
Very interested in this as well, I imagine an abstraction layer and a set of capability flags would make it easier to support other commerce backends without forcing everyone to implement the same common subset of features.
Edit: I should make it clear that one of those features is a checkout API as opposed to a hosted checkout view.
Quynh-Nguyen commentedon Nov 24, 2020
@okbel
Hi,
Can you please share your branch you working on this issue?
It's great if I can join to help for improve the implementation on it, because this is the most important feature.
32 remaining items
Fix Saleor's Demo link #2 (#363)
Merge pull request vercel#2 from chec/feature/pdp
Merge pull request #2 from DSCO-Co/product-page-initial
Merge pull request vercel#2 from okbel/arzafran/tweak-searchbox
Fix Saleor's Demo link vercel#2 (vercel#363)
Merge pull request vercel#2 from okbel/arzafran/tweak-searchbox
Fix Saleor's Demo link vercel#2 (vercel#363)
feat(session-13): B2B account, RBAC, audit, versioning, KPI, automation
Merge pull request vercel#2 from okbel/arzafran/tweak-searchbox
Fix Saleor's Demo link vercel#2 (vercel#363)
fix(migration): pre-apply discount on Stripe Checkout via prefilled p…
Merge pull request vercel#2 from lucaspulliese/add-license-1
feat: Phase 3 merch CTAs live — Stripe Prices + storefront wiring + w…
Merge pull request vercel#2 from okbel/arzafran/tweak-searchbox
Fix Saleor's Demo link vercel#2 (vercel#363)