Printing · Connected website
Kabbaj Print
A client website connected to ImpriPilot’s API, with catalogue publishing and quote requests managed from the business application.
Have a similar challenge?
Project study
About the project
Kabbaj Print combines a custom printing website with ImpriPilot’s Website module. The recorded walkthrough shows the public services catalogue, machine listings, catalogue publishing, category management, and incoming quote requests. Public article text can differ from the internal catalogue, and internal prices are not published. The captures show demonstration catalogue items and exclude private account and request details.
Project scope
- 01Custom website
- 02ImpriPilot API
- 03Catalogue & quote requests
Inside the project
Recorded walkthrough · Demonstration catalogue · Private account information excluded


The website and the business, connected
The catalogue is managed inside ImpriPilot.
The website presents services to visitors. ImpriPilot’s Website module provides article preparation, publication controls, and a workspace for incoming quote requests.
- 01ImpriPilotArticles and publication
- 02APIWebsite connection
- 03Kabbaj PrintCatalogue and quote requests
- Public copy separate from the internal catalogue
- Publish and unpublish controls
- Quote requests visible in the business workspace
- Internal prices kept out of the public website
How does this compare with WordPress or another CMS?
WordPress also provides an API. An API-based CMS such as Strapi can power a custom website too. This project’s distinction is its workflow: catalogue publishing and quote requests are handled within ImpriPilot’s Website module.
Scroll across the table to compare all approaches. →
| Comparison | WordPress | API-based CMS, such as Strapi | This project |
|---|---|---|---|
| Administration | Customisable WordPress editor and administration. | CMS administration and content models. | Website module inside ImpriPilot. |
| API connection | REST API available. | REST or GraphQL content API. | Connection to ImpriPilot’s API. |
| Business workflow | Integrations and extensions defined for the project. | Business logic connected to the CMS as required. | Catalogue publishing and quote requests shown in the walkthrough. |
The value here is having catalogue publishing and quote requests in the business tool already in use. Choosing a CMS or a custom integration depends on the content, workflows, and maintenance needs.
Documentation for the compared platforms :WordPress REST API — opens in a new tabStrapi Content API — opens in a new tabWooCommerce APIs — opens in a new tab
Recorded demonstration: catalogue examples do not represent sales or client results.