BigCommerce / Wordpress Headless Implementation - 3 Options
BigCommerce / Wordpress Headless implementations can be achieved in many ways, each with considerations the merchant must make. This article draws from Razoyo’s experience with real-world projects. BigCommerce has done an excellent job laying the groundwork for WordPress headless implementation through their adoption of the Open SaaS philosophy and the introduction of BC4WP.
BigCommerce’s plug-in for WordPress allows merchants to create their front-end experience on WP while managing the digital commerce aspects in BigCommerce. The merchant hosts a WP site and installs the plug in. The merchant also opens up a BC store. The WP plug in is responsible for syncing product data between the two sites and allowing WP to pull customer account and other data into the front end.
If implemented properly, the end experience for the shopper can be a completely seamless venture.
Some merchants ask, “why bother?” which is a legitimate question. WordPress has many benefits that are desirable for content-heavy sites including:
- Ease of styling - especially using the new Gutenberg theme editor
- Familiarity - marketing teams love to work in WordPress
- SEO-friendliness - WordPress is well-known for great SEO results due to its structure and popular plug-in tools for thinks like adding open-graph tags to content pages
- Easier content creation - with popular plug-ins like Yoast, you can make sure your content and blog pages attract search results
Three Key Options for BigCommerce / WordPress Headless
This version makes full use of the WordPress plug in. All actions by the shopper take place on the WordPress site and on the principle domain (www.yourshop.com). The merchant manages product catalogs, orders, customer accounts and so forth in BigCommerce. The plug in syncs products to WordPress and creates a page for each one along with a category hierarchy and so forth.
The customer never leaves the principle domain, everything is contained within the WordPress site.
In this scenario, the shopping experience takes place on the principle domain. WordPress is hosted on a separate domain, usually a subdomain like blog.yourshop.com. Care is taken to match the design of the header and footer on the sites to make the experience as seamless as possible.
Shop Centric implementations generally put all content on BigCommerce except for the blog itself.
In this case, the home page would definitely be hosted by WordPress and when shopping, the user will be ‘escorted’ to a subdomain like shop.yourshop.com. A purely blog-centric implementation would only use the BC catalog for shopping pages (catalog, product detail, cart and checkout).