Overview

introduction sparklayer ignite is a commerce framework that enables any platform to easily integrate with the power of sparklayer from delivering a world class frontend b2b self service ordering experience, to connecting to sparklayer's extensive b2b pricing engine use cases the most common use case is to use sparklayer ignite alongside a complimentary ecommerce platform or content management system (cms) for example, an ecommerce platform may have very limited b2b ecommerce functionality and it's not viable to build it natively by connecting the ecommerce platform to sparklayer ignite (e g via a custom application), b2b functionality can be rapidly enabled please note access to sparklayer ignite requires https //share eu1 hsforms com/1zsi9nes5swgyrx9kvwia2wfkn6z that our team will review as part of the approval process, we will evaluate applications to ensure sparklayer is a good match for the relevant use case, both technically and strategically before starting our documentation covers all key principles and concepts required to build an integration via the sparklayer ignite framework this includes how to connect a platform (e g an ecommerce platform) and synchronise data, right through to connecting to specific endpoints to allow you to customise as you need to in order to familiarise yourself with how sparklayer works, we recommend reviewing the following guides true left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type key principles understanding the data flow understanding how data flows between sparklayer and a platform (e g an ecommerce platform) is central to building an integration at a very top level, our diagram below illustrates the key data flows platform connection platform connection is the term used for when a platform is connected to sparklayer (e g an ecommerce platform) there are two endpoints one to inform of new connection another to inform once it's removed learn more about https //docs sparklayer io/ignite/x 67 platform connection data sync overview sparklayer requires data from the platform in order to operate when an install initially happens, a full sync will be required to begin the process for further updates, webhooks should power these incremental changes with the option to run the sync again (in case of any issues) for visibility, data sync issues should also be logged within the https //docs sparklayer io/sparklayer dashboard/the sparklayer dashboard/customers#customer import for easy review data should include true left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type learn more about the https //docs sparklayer io/ignite/data sync endpoints the below are required instantly on a customer request and these endpoints will outline the request body and response body true left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type learn more about the https //docs sparklayer io/ignite/endpoints overview please note the following currently, these areas are excluded from this documentation and will be covered in due course or elsewhere billing and any sparklayer dashboard logic sparklayer currently only supports a single storefront per sparklayer environment sparklayer currently only supports simple option products, i e complex bundles are unsupported