Market and technology trends have created a digital transformation imperative in retail. Accelerator for Retail includes pre-built APIs and a prescriptive architecture to help IT teams jumpstart the development of common retail applications and provides a foundation for 3x faster project delivery.
- Support for core business processes – Retail processes like customer onboarding, product availability, and fulfillment require real-time integration across eCommerce, CRMs, and other core systems of record.
- Architecture best practice – Accelerator for Retail provides a proposed architecture – one drawn from working with industry leaders – that promotes asset self-service and reuse.
- Pre-built API designs and implementations – With omnichannel driving today’s retail, MuleSoft has built a set of omnichannel specific APIs that build on GS1 standards and integrate on the top of retail process and system APIs.
API-Led Microservices Architecture for Retail
In addition to providing pre-built APIs, Accelerator for Retail includes a model for API-led connectivity in retail that promotes asset reuse and self-service. In the above architecture, we’ve abstracted data from complex retail systems like Hybris, Salesforce and Partner systems that use EDI messages into a canonical model that is represented via a set of REST APIs. Then, we built experience APIs that provide better experiences for both customers and API consumers.
System APIs abstract away the complexity of core retail systems of record from the end user, while providing downstream insulation from any interface changes or rationalization of those systems.
- Customer System API | RAML Definition
- Customer System API | Salesforce Implementation Template
- Order System API | RAML Definition
- Order System API | Salesforce Implementation Template
- Product API | RAML Definition
- Product API | Hybris Implementation Template
- Inventory API | RAML Definition
- Inventory API | Hybris Implementation Template (Coming soon)
- Partners API | RAML definition
- Partners API | Partner Implementation Template
- Location API | RAML Definition
- Location API | MySQL Implementation Template
- Notification API | Gmail and Twillio Implementation Template
Process APIs decouple business processes that interact with and shape data from the source systems where the data originated. For example, the “Payment Process API” contains logic that is common across multiple entities, which can be called by product, geography, or channel-specific parent services.
- Customer Onboarding API | RAML Definition
- Customer Onboarding API | Implementation Template
- Product Availability API | RAML Definition
- Product Availability API | Implementation Template
- Order Fulfilment API | RAML Definition
- Order Fulfilment API | Implementation Template
- Payment API | RAML Definition (Coming soon)
- Shopping Cart API | RAML Definition
- Shopping Cart API | Implementation Template
Experience APIs are the means by which data can be reconfigured so that it is most easily consumed by its intended audience, all from a common data source, rather than setting up separate point-to-point integrations.
- Omnichannel API | RAML Definition
- Omnichannel API | Implementation Template
- Anypoint Store - Conversational Commerce | Implementation Template
Give it a try and if you have questions or feedback, let us know at firstname.lastname@example.org.