BigCommerce brings customised shopping experiences to Drupal
FYI, this story is more than a year old
BigCommerce announced BigCommerce for Drupal, a headless commerce module built specifically for the open-source content management system (CMS).
Developed in partnership with Acro Media, a world-renowned digital commerce agency, BigCommerce for Drupal gives brands the ability to embed flexible, enterprise-level e-commerce functionality into revolutionary customer experiences created within Drupal’s highly-extensible and secure CMS.
Available in the Drupal module library, BigCommerce for Drupal aims to facilitate an agile headless commerce architecture for merchants by decoupling Drupal’s powerful front-end CMS and BigCommerce’s scalable commerce engine.
Knitted together by fast, open-source APIs, the module supposedly allows the two platforms to operate simultaneously and more efficiently within a single interface. Additionally, BigCommerce for Drupal is built directly into Drupal Commerce, making it compatible with the many existing themes and modules available within Drupal Commerce.
BigCommerce chief development officer Russell Klein says, “Shopping experiences should not be limited by any single content management or e-commerce platform’s native capabilities, and BigCommerce for Drupal embodies that philosophy. We want pioneering brands to continue driving retail innovation forward and help redefine how customers buy products, whether it be through augmented reality, social selling or any disruptive technology that lies ahead.
Key features of BigCommerce for Drupal include:
- Drupal Commerce Core: BigCommerce for Drupal is built atop the Drupal Commerce module, developed in part by Acro Media, tapping into years of iterative improvements and enhancements.
- Data Sync: With BigCommerce for Drupal, retailers can synchronise product and metadata directly from BigCommerce into Drupal, and then augment and manage data directly within the Drupal CMS.
- Cached Commerce: The connected BigCommerce store will sync at merchant-determined intervals, saving a cached version of the catalogue inside Drupal rather than pinging BigCommerce APIs for information.