[go: nahoru, domu]
Jump to content

Headless commerce: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous edit
Content deleted Content added
VisualWikitext
Add link to Commercetools article
Crispyhull (talk | contribs)
498 edits
definitions were wrong way around so switched “former” and “latter” #article-section-source-editor
Tags: Mobile edit Mobile app edit iOS app edit
 
(5 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{Cleanup bare URLs|date=August 2022}}
{{Cleanup bare URLs|date=August 2022}}
'''Headless commerce''' is an [[e-commerce]] [[Building information modeling|architecture]] where the [[Front end and back end|front-end]] (head) is decoupled from the back-end commerce functionality and can thus be updated or edited without interfering with the back-end, similar to a [[Headless content management system|headless content management system (CMS)]].<ref name=":2">{{Cite web|title=The Ultimate Guide to Headless Commerce {{!}} Bloomreach|url=https://www.bloomreach.com/en/blog/2019/08/headless-commerce.html|access-date=2021-03-09|website=bloomreach.com|language=en}}</ref> The term was coined by Dirk Hoerig, [[Organizational founder|co-founder]] of [[Commercetools]], in 2013.<ref name=":0">{{Cite web|last=Cicman|first=Joe|date=2019-08-13|title=Headless Commerce And The Horseless Carriage|url=https://go.forrester.com/blogs/headless-commerce-and-the-horseless-carriage/|url-status=live|access-date=2021-03-09|website=Forrester|language=en-US}}</ref>
'''Headless commerce''' is an [[e-commerce]] [[Building information modeling|architecture]] where the [[Front end and back end|front-end]] (head) is decoupled from the back-end commerce functionality and can thus be updated or edited without interfering with the back-end, similar to a [[Headless content management system|headless content management system (CMS)]].<ref name=":2">{{Cite web|title=The Ultimate Guide to Headless Commerce {{!}} Bloomreach|url=https://www.bloomreach.com/en/blog/2019/08/headless-commerce.html|access-date=2021-03-09|website=bloomreach.com|language=en}}</ref> The term was coined by Dirk Hoerig, [[Organizational founder|co-founder]] of [[Commercetools]], in 2013.<ref name=":0">{{Cite web|last=Cicman|first=Joe|date=2019-08-13|title=Headless Commerce And The Horseless Carriage|url=https://go.forrester.com/blogs/headless-commerce-and-the-horseless-carriage/|access-date=2021-03-09|website=Forrester|language=en-US}}</ref>


== History ==
== History ==
Headless commerce was arguably born out of a 2013 [[Forrester Research]] report that bemoaned e-commerce vendors falling behind [[user experience]] trends and recommended “loosely” coupling the back- and front-ends of e-commerce stores.<ref name=":0" /><ref>{{Cite web|last1=Powers|first1=Stephen|last2=Sheldon|first2=Peter|date=2013-11-19|title=Content And Commerce: The Odd Couple Or The Power Couple?|url=https://www.forrester.com/report/Content+And+Commerce+The+Odd+Couple+Or+The+Power+Couple/-/E-RES108141|url-status=live|access-date=2021-03-10|website=www.forrester.com}}</ref>
Headless commerce was arguably born out of a 2013 [[Forrester Research]] report that bemoaned e-commerce vendors falling behind [[user experience]] trends and recommended “loosely” coupling the back- and front-ends of e-commerce stores.<ref name=":0" /><ref>{{Cite web|last1=Powers|first1=Stephen|last2=Sheldon|first2=Peter|date=2013-11-19|title=Content And Commerce: The Odd Couple Or The Power Couple?|url=https://www.forrester.com/report/Content+And+Commerce+The+Odd+Couple+Or+The+Power+Couple/-/E-RES108141|access-date=2021-03-10|website=www.forrester.com}}</ref>


== Architecture ==
== Architecture ==
Headless commerce architecture passes requests between a platform's [[Presentation layer|presentation]] and application layers.<ref name=":3">{{Cite web|last=Lewis|first=Sarah|title=What is Headless Commerce? Definition from WhatIs.com|url=https://searchcustomerexperience.techtarget.com/definition/headless-commerce-headless-e-commerce|url-status=live|access-date=2021-03-09|website=SearchCustomerExperience|language=en}}</ref> The presentation layer is connected with the e-commerce functionality via [[Representational state transfer|REST]] [[API]]s, or application programming interfaces, which define interactions between multiple software intermediaries.<ref name=":1">{{Cite book|last=Goetsch|first=Kelly|url=https://cdn2.hubspot.net/hubfs/4784080/Files/Website%20PDFs/EN/Other%20Studies/commercetools_Booklet_APIs_for_Modern_Commerce(EN).pdf|title=APIs for Modern Commerce|publisher=[[O'Reilly Media]]|year=2017|isbn=9781491995259|pages=2, 7}}</ref><ref>{{Cite web|last=Sam|first=Saltis|title=Headless Commerce: The Definitive Guide [2021 Edition]|url=https://www.coredna.com/blogs/headless-commerce|url-status=live|access-date=2021-03-09|website=www.coredna.com}}</ref> This allows businesses to change customer-facing experiences without disrupting backend functionality and to update, edit or change products and distribute via API to multiple front-ends.<ref name=":1" /> REST APIs are the backbone of this architecture.<ref>{{Cite web|last=Nacelle|title=The History of Headless Storefronts|url=https://nacelle.com/blog/the-history-of-headless-storefronts|access-date=2021-03-09|website=Nacelle|language=en}}</ref>
Headless commerce architecture passes requests between a platform's [[Presentation layer|presentation]] and application layers.<ref name=":3">{{Cite web|last=Lewis|first=Sarah|title=What is Headless Commerce? Definition from WhatIs.com|url=https://searchcustomerexperience.techtarget.com/definition/headless-commerce-headless-e-commerce|access-date=2021-03-09|website=SearchCustomerExperience|language=en}}</ref> The presentation layer is connected with the e-commerce functionality via [[Representational state transfer|REST]] [[API]]s, or application programming interfaces, which define interactions between multiple software intermediaries.<ref name=":1">{{Cite book|last=Goetsch|first=Kelly|url=https://cdn2.hubspot.net/hubfs/4784080/Files/Website%20PDFs/EN/Other%20Studies/commercetools_Booklet_APIs_for_Modern_Commerce(EN).pdf|title=APIs for Modern Commerce|publisher=[[O'Reilly Media]]|year=2017|isbn=9781491995259|pages=2, 7}}</ref><ref>{{Cite web|last=Sam|first=Saltis|title=Headless Commerce: The Definitive Guide [2021 Edition]|url=https://www.coredna.com/blogs/headless-commerce|access-date=2021-03-09|website=www.coredna.com}}</ref> This allows businesses to change customer-facing experiences without disrupting backend functionality and to update, edit or change products and distribute via API to multiple front-ends.<ref name=":1" /> REST APIs are the backbone of this architecture.<ref>{{Cite web|last=Nacelle|title=The History of Headless Storefronts|url=https://nacelle.com/blog/the-history-of-headless-storefronts|access-date=2021-03-09|website=Nacelle|language=en}}</ref>


== Coupled e-commerce vs headless e-commerce ==
== Coupled e-commerce vs headless e-commerce ==
Headless commerce is distinct from coupled, traditional or “monolithic” e-commerce in that the former relies on a front-end and back-end that function together and the latter comprises solely a back-end which communicates with front-ends via APIs.<ref>{{Cite web|last=Lynch|first=Paul|date=2021-01-05|title=How will headless commerce change your retail experience?|url=https://www.itproportal.com/features/how-will-headless-commerce-change-your-retail-experience/|url-status=live|access-date=2021-03-09|website=ITProPortal|language=en}}</ref>
Headless commerce is distinct from coupled, traditional or “monolithic” e-commerce in that the latter relies on a front-end and back-end that function together and the former comprises solely a back-end which communicates with front-ends via APIs.<ref>{{Cite web|last=Lynch|first=Paul|date=2021-01-05|title=How will headless commerce change your retail experience?|url=https://www.itproportal.com/features/how-will-headless-commerce-change-your-retail-experience/|access-date=2021-03-09|website=ITProPortal|language=en}}</ref>


Headless commerce platforms offer advantages over traditional [[Shopping cart software|e-commerce platforms]] in that changes to data and functionality only need to be made in a single back-end, with all front-ends then having immediate access to those changes. Likewise, each front-end can then be changed and deployed without impacting the back-end.<ref name=":1" /> Another difference is that many traditional e-commerce platforms come with predefined front-end [[Web template system|templates]] or customization, whereas headless commerce can power any front-end via APIs.<ref name=":6">{{Cite web|last=Katie|first=Evans|date=2021-02-01|title=Bed tent retailer Privacy Pop lays out the benefits of moving to headless commerce|url=https://www.digitalcommerce360.com/2021/02/01/bed-tent-retailer-privacy-pop-lays-out-the-benefits-of-moving-to-headless-commerce/|url-status=live|access-date=2021-03-09|website=Digital Commerce 360|language=en-US}}</ref>
Headless commerce platforms offer advantages over traditional [[Shopping cart software|e-commerce platforms]] in that changes to data and functionality only need to be made in a single back-end, with all front-ends then having immediate access to those changes. Likewise, each front-end can then be changed and deployed without impacting the back-end.<ref name=":1" /> Another difference is that many traditional e-commerce platforms come with predefined front-end [[Web template system|templates]] or customization, whereas headless commerce can power any front-end via APIs.<ref name=":6">{{Cite web|last=Katie|first=Evans|date=2021-02-01|title=Bed tent retailer Privacy Pop lays out the benefits of moving to headless commerce|url=https://www.digitalcommerce360.com/2021/02/01/bed-tent-retailer-privacy-pop-lays-out-the-benefits-of-moving-to-headless-commerce/|access-date=2021-03-09|website=Digital Commerce 360|language=en-US}}</ref>


Headless commerce platforms require more work and customization than traditional platforms and are often not suitable for [[Small business|smaller businesses]].<ref name=":5">{{Cite web|last=Szatvanyi|first=Gerard|title=Council Post: Is Headless Commerce The Solution For Your Business?|url=https://www.forbes.com/sites/forbestechcouncil/2019/06/03/is-headless-commerce-the-solution-for-your-business/|access-date=2021-03-09|website=Forbes|language=en}}</ref> Such platforms lack predesigned templates and do not provide all-in-one solutions. Headless commerce platforms also require [[Web developer|developers]] to build or buy a separate front-end.<ref>{{Cite web|last=Levitz|first=Michael|date=2021-02-10|title=3 Ways Covid Changed E-Commerce Forever|url=https://www.inc.com/michael-levitz/3-ways-covid-changed-e-comforever.html|access-date=2021-03-09|website=Inc.com|language=en}}</ref>
Headless commerce platforms require more work and customization than traditional platforms and are often not suitable for [[Small business|smaller businesses]].<ref name=":5">{{Cite web|last=Szatvanyi|first=Gerard|title=Council Post: Is Headless Commerce The Solution For Your Business?|url=https://www.forbes.com/sites/forbestechcouncil/2019/06/03/is-headless-commerce-the-solution-for-your-business/|access-date=2021-03-09|website=Forbes|language=en}}</ref> Such platforms lack predesigned templates and do not provide all-in-one solutions. Headless commerce platforms also require [[Web developer|developers]] to build or buy a separate front-end.<ref>{{Cite web|last=Levitz|first=Michael|date=2021-02-10|title=3 Ways Covid Changed E-Commerce Forever|url=https://www.inc.com/michael-levitz/3-ways-covid-changed-e-comforever.html|access-date=2021-03-09|website=Inc.com|language=en}}</ref>
Line 18: Line 18:


=== Flexibility ===
=== Flexibility ===
The front-ends and back-ends of a headless system are decoupled, making it possible to change the content layer without disrupting business. This creates flexibility to allow the front- and back-ends to work independently and create new [[user experience]]s without compromising old ones.<ref name=":4">{{Cite web|last=Chavan|first=Satish|date=2018-12-05|title=What is 'headless commerce' and why it is growing in popularity?|url=https://www.digitalcommerce360.com/2018/12/05/what-is-headless-commerce-and-why-it-is-growing-in-popularity/|url-status=live|access-date=2021-03-09|website=Digital Commerce 360|language=en-US}}</ref> There is also no confining code that restricts delivery to [[internet of things]] devices, [[Application software|applications]], [[web browser]]s or other end points.<ref name=":2" />
The front-ends and back-ends of a headless system are decoupled, making it possible to change the content layer without disrupting business. This creates flexibility to allow the front- and back-ends to work independently and create new [[user experience]]s without compromising old ones.<ref name=":4">{{Cite web|last=Chavan|first=Satish|date=2018-12-05|title=What is 'headless commerce' and why it is growing in popularity?|url=https://www.digitalcommerce360.com/2018/12/05/what-is-headless-commerce-and-why-it-is-growing-in-popularity/|access-date=2021-03-09|website=Digital Commerce 360|language=en-US}}</ref> There is also no confining code that restricts delivery to [[internet of things]] devices, [[Application software|applications]], [[web browser]]s or other end points.<ref name=":2" />


=== Speed ===
=== Speed ===
Line 27: Line 27:


=== Unified user experience ===
=== Unified user experience ===
Headless commerce allows a business to control all customer touchpoints at once.<ref>{{Cite web|last=Ismail|first=Kaya|title=Why Enterprise eCommerce Should Be Adopting the MACH Architecture|url=https://www.cmswire.com/information-management/why-enterprise-ecommerce-needs-to-adopt-mach/|url-status=live|access-date=2021-04-19|website=CMSWire.com|language=en}}</ref> This creates a consistent customer experience across different front-ends that enable customers to complete a purchase at any touch point.<ref name=":5" />
Headless commerce allows a business to control all customer touchpoints at once.<ref>{{Cite web|last=Ismail|first=Kaya|title=Why Enterprise eCommerce Should Be Adopting the MACH Architecture|url=https://www.cmswire.com/information-management/why-enterprise-ecommerce-needs-to-adopt-mach/|access-date=2021-04-19|website=CMSWire.com|language=en}}</ref> This creates a consistent customer experience across different front-ends that enable customers to complete a purchase at any touch point.<ref name=":5" />


== Headless commerce providers ==
== Headless commerce providers ==
* Dynamics 365 Commerce<ref>{{cite web | url=https://learn.microsoft.com/en-us/dynamics365/commerce/dev-itpro/retail-server-architecture | title=Headless commerce architecture - Commerce &#124; Dynamics 365 | date=12 August 2022 }}</ref>
*Brink Commerce <ref>{{Cite web |date=2021-10-05 |title=Brink Commerce secures SEK 20 million. Nordic 9 |url=https://nordic9.com/news/brink-commerce-secures-sek-20-million/ |access-date=2022-05-16 |website=Nordic9 |language=en-US}}</ref>
*Brink Commerce <ref>{{Cite web |date=2021-10-05 |title=Brink Commerce secures SEK 20 million. Nordic 9 |url=https://nordic9.com/news/brink-commerce-secures-sek-20-million/ |access-date=2022-05-16 |website=Nordic9 |language=en-US}}</ref>
*Swell<ref>{{Cite web|title=Headless commerce startup Swell raises $3.4M|url=https://social.techcrunch.com/2021/03/26/headless-commerce-startup-swell-raises-3-4m/|access-date=2021-06-19|website=TechCrunch|date=26 March 2021 |language=en-US}}</ref>
*Swell<ref>{{Cite web|title=Headless commerce startup Swell raises $3.4M|url=https://social.techcrunch.com/2021/03/26/headless-commerce-startup-swell-raises-3-4m/|access-date=2021-06-19|website=TechCrunch|date=26 March 2021 |language=en-US}}</ref>
*Shogun<ref>{{Cite web|last=Lunden|first=Ingrid|title=Shogun, a front-end e-commerce page builder, nabs $67.5M as retailers look for alternatives to marketplaces|url=https://techcrunch.com/2021/06/30/shogun-a-front-end-e-commerce-page-builder-nabs-67-5m-as-retailers-look-for-alternatives-to-marketplaces/|access-date=2021-10-19|website=TechCrunch|date=30 June 2021 |language=en-US}}</ref>
*Shogun<ref>{{Cite web|last=Lunden|first=Ingrid|title=Shogun, a front-end e-commerce page builder, nabs $67.5M as retailers look for alternatives to marketplaces|url=https://techcrunch.com/2021/06/30/shogun-a-front-end-e-commerce-page-builder-nabs-67-5m-as-retailers-look-for-alternatives-to-marketplaces/|access-date=2021-10-19|website=TechCrunch|date=30 June 2021 |language=en-US}}</ref>
*Commerce.js<ref>{{Cite web|last=Stone|first=Madeline|title=8 Headless Commerce Startups Using Tech First Used By Amazon|url=https://www.businessinsider.com/headless-commerce-startups-raising-the-most-vc-funds-2021-8|access-date=2021-10-19|website=Business Insider|language=en-US}}</ref>
*Commerce.js<ref>{{Cite web|last=Stone|first=Madeline|title=8 Headless Commerce Startups Using Tech First Used By Amazon|url=https://www.businessinsider.com/headless-commerce-startups-raising-the-most-vc-funds-2021-8|access-date=2021-10-19|website=Business Insider|language=en-US}}</ref>
*[[Oracle Advertising and Customer Experience (CX)|Oracle CX]] Commerce <ref>{{Cite web|last=Nathan|first=Joynt|date=June 15, 2018|title=What is Headless Commerce?|url=https://blogs.oracle.com/cx/post/what-is-headless-commerce|url-status=live|website=Oracle Blog}}</ref>
*[[Oracle Advertising and Customer Experience (CX)|Oracle CX]] Commerce <ref>{{Cite web|last=Nathan|first=Joynt|date=June 15, 2018|title=What is Headless Commerce?|url=https://blogs.oracle.com/cx/post/what-is-headless-commerce|website=Oracle Blog}}</ref>
*[[Shopify]]<ref name=":7">{{Cite web|last=Ha|first=Anthony|title='Headless' e-commerce platform Fabric raises $43M|url=https://social.techcrunch.com/2021/02/09/fabric-series-a/|url-status=live|access-date=2021-03-10|website=TechCrunch|language=en-US}}</ref>
*[[Shopify]]<ref name=":7">{{Cite web|last=Ha|first=Anthony|title='Headless' e-commerce platform Fabric raises $43M|url=https://social.techcrunch.com/2021/02/09/fabric-series-a/|access-date=2021-03-10|website=TechCrunch|date=9 February 2021 |language=en-US}}</ref>
* [[Magento]]<ref name=":8">{{Cite web|last=Diaz|first=Olivia|date=2019-04-09|title=Why should your e-commerce site opt for Headless Magento 2?|url=https://hub.packtpub.com/why-should-your-e-commerce-site-opt-for-headless-magento-2/|url-status=live|access-date=2021-03-10|website=Packt Hub|language=en-US}}</ref>
* [[Magento]]<ref name=":8">{{Cite web|last=Diaz|first=Olivia|date=2019-04-09|title=Why should your e-commerce site opt for Headless Magento 2?|url=https://hub.packtpub.com/why-should-your-e-commerce-site-opt-for-headless-magento-2/|access-date=2021-03-10|website=Packt Hub|language=en-US}}</ref>
* [[Commercetools]]<ref>{{Cite web|last=Bradford|first=Rodric|date=2020-09-04|title=This week in martech|url=https://martechtoday.com/this-week-in-martech-7-243720|url-status=live|access-date=2021-03-10|website=MarTech Today|language=en}}</ref>
* [[Commercetools]]<ref>{{Cite web|last=Bradford|first=Rodric|date=2020-09-04|title=This week in martech|url=https://martechtoday.com/this-week-in-martech-7-243720|access-date=2021-03-10|website=MarTech Today|language=en}}</ref>
* [https://crystallize.com Crystallize]
* [https://crystallize.com Crystallize]
* Fabric<ref name=":7" />
* Fabric<ref name=":7" />
Line 43: Line 44:
* Nacelle<ref name=":6" />
* Nacelle<ref name=":6" />
* BigCommerce<ref name=":8" />
* BigCommerce<ref name=":8" />
* Slatwall Commerce<ref name=":9">{{Cite web|last=Kreschollek|first=Steven|date=2021-07-15|title=Headless Commerce: A Primer|url=https://eightfold.io/blog/headless-e-commerce-a-primer/|url-status=live|access-date=2021-07-23|website=Eightfold|language=en-US}}</ref>
* Slatwall Commerce<ref name=":9">{{Cite web|last=Kreschollek|first=Steven|date=2021-07-15|title=Headless Commerce: A Primer|url=https://eightfold.io/blog/headless-e-commerce-a-primer/|access-date=2021-07-23|website=Eightfold|language=en-US}}</ref>
*Bagisto<ref>{{Citation|title=Bagisto GraphQL API|date=2021-10-09|url=https://github.com/bagisto/headless-ecommerce|publisher=Bagisto|access-date=2021-10-29}}</ref>
*Bagisto<ref>{{Citation|title=Bagisto GraphQL API|date=2021-10-09|url=https://github.com/bagisto/headless-ecommerce|publisher=Bagisto|access-date=2021-10-29}}</ref>
*Enkarto<ref>{{Cite web |title=Enkarto |url=https://www.enkarto.com/ |url-status=live |access-date=2023-03-21 |website=Enkarto}}</ref>
* Slixta<ref>https://slixta.com/</ref>
* Slixta<ref>https://slixta.com/</ref>
* bl!nk<ref>{{cite web | url=https://responsival.com/blink/ | title=Bl!nk &#124; Headless Shopify experiences that load in the blink-of-an-eye }}</ref>
* bl!nk<ref>{{cite web | url=https://responsival.com/blink/ | title=Bl!nk &#124; Headless Shopify experiences that load in the blink-of-an-eye }}</ref>
Line 53: Line 53:
*SAP Commerce Cloud
*SAP Commerce Cloud
*Rierino<ref>{{Cite web |last=Ozmen |first=Mine |date=2021-12-23 |title=Headless Commerce: Why is everyone losing their head? |url=https://medium.com/rierino/headless-commerce-why-and-how-rierino-pov-625d702d47c7 |access-date=2022-10-20 |website=Rierino |language=en}}</ref>
*Rierino<ref>{{Cite web |last=Ozmen |first=Mine |date=2021-12-23 |title=Headless Commerce: Why is everyone losing their head? |url=https://medium.com/rierino/headless-commerce-why-and-how-rierino-pov-625d702d47c7 |access-date=2022-10-20 |website=Rierino |language=en}}</ref>
* TheShop Management<ref>https://theshop.management/</ref>



== References ==
== References ==

Latest revision as of 08:18, 28 March 2024

Headless commerce is an e-commerce architecture where the front-end (head) is decoupled from the back-end commerce functionality and can thus be updated or edited without interfering with the back-end, similar to a headless content management system (CMS).[1] The term was coined by Dirk Hoerig, co-founder of Commercetools, in 2013.[2]

History[edit]

Headless commerce was arguably born out of a 2013 Forrester Research report that bemoaned e-commerce vendors falling behind user experience trends and recommended “loosely” coupling the back- and front-ends of e-commerce stores.[2][3]

Architecture[edit]

Headless commerce architecture passes requests between a platform's presentation and application layers.[4] The presentation layer is connected with the e-commerce functionality via REST APIs, or application programming interfaces, which define interactions between multiple software intermediaries.[5][6] This allows businesses to change customer-facing experiences without disrupting backend functionality and to update, edit or change products and distribute via API to multiple front-ends.[5] REST APIs are the backbone of this architecture.[7]

Coupled e-commerce vs headless e-commerce[edit]

Headless commerce is distinct from coupled, traditional or “monolithic” e-commerce in that the latter relies on a front-end and back-end that function together and the former comprises solely a back-end which communicates with front-ends via APIs.[8]

Headless commerce platforms offer advantages over traditional e-commerce platforms in that changes to data and functionality only need to be made in a single back-end, with all front-ends then having immediate access to those changes. Likewise, each front-end can then be changed and deployed without impacting the back-end.[5] Another difference is that many traditional e-commerce platforms come with predefined front-end templates or customization, whereas headless commerce can power any front-end via APIs.[9]

Headless commerce platforms require more work and customization than traditional platforms and are often not suitable for smaller businesses.[10] Such platforms lack predesigned templates and do not provide all-in-one solutions. Headless commerce platforms also require developers to build or buy a separate front-end.[11]

Headless commerce may be preferred from a quality assurance perspective, as traditional e-commerce platforms face a higher risk of making changes that could disrupt operations, since the front end and back end are coupled.[4] Because headless commerce communicates with the front-end via APIs and there is no code intertwined with the backend database that stores content, frontend developers can adapt endpoint layout as needed with no disruptions to the customer experience.[1]

Flexibility[edit]

The front-ends and back-ends of a headless system are decoupled, making it possible to change the content layer without disrupting business. This creates flexibility to allow the front- and back-ends to work independently and create new user experiences without compromising old ones.[12] There is also no confining code that restricts delivery to internet of things devices, applications, web browsers or other end points.[1]

Speed[edit]

The decoupled architecture of headless commerce enables developers to make quick changes, such as implementing new functionalities and integrations without disrupting the back end.[12]

Personalization[edit]

Headless commerce allows for the creation of customized designs and layouts for different endpoints, since front-end design can be changed without impacting the back-end.[13][14]

Unified user experience[edit]

Headless commerce allows a business to control all customer touchpoints at once.[15] This creates a consistent customer experience across different front-ends that enable customers to complete a purchase at any touch point.[10]

Headless commerce providers[edit]


References[edit]

  1. ^ a b c "The Ultimate Guide to Headless Commerce | Bloomreach". bloomreach.com. Retrieved 2021-03-09.
  2. ^ a b Cicman, Joe (2019-08-13). "Headless Commerce And The Horseless Carriage". Forrester. Retrieved 2021-03-09.
  3. ^ Powers, Stephen; Sheldon, Peter (2013-11-19). "Content And Commerce: The Odd Couple Or The Power Couple?". www.forrester.com. Retrieved 2021-03-10.
  4. ^ a b Lewis, Sarah. "What is Headless Commerce? Definition from WhatIs.com". SearchCustomerExperience. Retrieved 2021-03-09.
  5. ^ a b c Goetsch, Kelly (2017). APIs for Modern Commerce (PDF). O'Reilly Media. pp. 2, 7. ISBN 9781491995259.
  6. ^ Sam, Saltis. "Headless Commerce: The Definitive Guide [2021 Edition]". www.coredna.com. Retrieved 2021-03-09.
  7. ^ Nacelle. "The History of Headless Storefronts". Nacelle. Retrieved 2021-03-09.
  8. ^ Lynch, Paul (2021-01-05). "How will headless commerce change your retail experience?". ITProPortal. Retrieved 2021-03-09.
  9. ^ a b Katie, Evans (2021-02-01). "Bed tent retailer Privacy Pop lays out the benefits of moving to headless commerce". Digital Commerce 360. Retrieved 2021-03-09.
  10. ^ a b Szatvanyi, Gerard. "Council Post: Is Headless Commerce The Solution For Your Business?". Forbes. Retrieved 2021-03-09.
  11. ^ Levitz, Michael (2021-02-10). "3 Ways Covid Changed E-Commerce Forever". Inc.com. Retrieved 2021-03-09.
  12. ^ a b Chavan, Satish (2018-12-05). "What is 'headless commerce' and why it is growing in popularity?". Digital Commerce 360. Retrieved 2021-03-09.
  13. ^ "What Is Headless Commerce?". CB Insights Research. Retrieved 2021-03-09.
  14. ^ "Understanding Headless Commerce And Why It's Better for the Customer". Retail Minded. 2019-01-07. Retrieved 2021-03-09.
  15. ^ Ismail, Kaya. "Why Enterprise eCommerce Should Be Adopting the MACH Architecture". CMSWire.com. Retrieved 2021-04-19.
  16. ^ "Headless commerce architecture - Commerce | Dynamics 365". 12 August 2022.
  17. ^ "Brink Commerce secures SEK 20 million. Nordic 9". Nordic9. 2021-10-05. Retrieved 2022-05-16.
  18. ^ "Headless commerce startup Swell raises $3.4M". TechCrunch. 26 March 2021. Retrieved 2021-06-19.
  19. ^ Lunden, Ingrid (30 June 2021). "Shogun, a front-end e-commerce page builder, nabs $67.5M as retailers look for alternatives to marketplaces". TechCrunch. Retrieved 2021-10-19.
  20. ^ Stone, Madeline. "8 Headless Commerce Startups Using Tech First Used By Amazon". Business Insider. Retrieved 2021-10-19.
  21. ^ Nathan, Joynt (June 15, 2018). "What is Headless Commerce?". Oracle Blog.
  22. ^ a b c Ha, Anthony (9 February 2021). "'Headless' e-commerce platform Fabric raises $43M". TechCrunch. Retrieved 2021-03-10.
  23. ^ a b Diaz, Olivia (2019-04-09). "Why should your e-commerce site opt for Headless Magento 2?". Packt Hub. Retrieved 2021-03-10.
  24. ^ Bradford, Rodric (2020-09-04). "This week in martech". MarTech Today. Retrieved 2021-03-10.
  25. ^ Kreschollek, Steven (2021-07-15). "Headless Commerce: A Primer". Eightfold. Retrieved 2021-07-23.
  26. ^ Bagisto GraphQL API, Bagisto, 2021-10-09, retrieved 2021-10-29
  27. ^ https://slixta.com/
  28. ^ "Bl!nk | Headless Shopify experiences that load in the blink-of-an-eye".
  29. ^ https://www.pcommerce.it
  30. ^ "Vetrina Live – Ecommerce platform made easy for everyone". Retrieved 2022-06-10.
  31. ^ "Elastic Path: Enterprise Digital Commerce Made Simple". Elastic Path. Retrieved 2022-07-26.
  32. ^ Ozmen, Mine (2021-12-23). "Headless Commerce: Why is everyone losing their head?". Rierino. Retrieved 2022-10-20.
  33. ^ https://theshop.management/

See also[edit]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Headless_commerce&oldid=1215975115"