Marketplace. Buyers and sellers, one plane.
Coordinate seller guidance, buyer notices and bilingual marketplace content.
Marketplace content must serve buyers and sellers across onboarding, catalogue preparation and live order states. Release cycles can leave instructions and labels behind fast operational changes, especially during seasonal demand peaks.
Buyers and sellers, one plane.
One change, end to end.
One segment definition, reused everywhere, so buyer and seller targeting cannot drift apart.
Sensors is in preview and available to selected workspaces behind a feature flag. Illustrative interface content.
What makes it hard.
Seller activation friction
New sellers need clear sequencing across identity checks, catalogue setup and first-listing preparation.
Seasonal demand peaks
Ramadan and Hajj can compress the time available to update collection guidance, seller instructions and operational notices.
Buyer trust signals
Order and collection notices must reflect the marketplace's recorded state without creating uncertainty about availability or location.
Four things a team could build.
Activate new sellers
A marketplace could guide a new seller through identity checks, catalogue setup and first-listing preparation. Journeys would coordinate the relevant content steps using events supplied by the marketplace.
JourneysManage bilingual seller content
A Saudi marketplace could provide seller instructions in Arabic and English from one managed content structure. Localization would serve the selected version while preserving configured fallback behaviour.
LocalizationSend order collection notices
A marketplace could notify a buyer when an order is ready for collection at a selected location. Messaging Channels would send the approved notice after receiving the relevant order event.
Messaging ChannelsObserve renamed menu labels
A marketplace could enable a renamed menu label as a sensor to collect view signals when users reach it. Sensors is in preview behind a feature flag, and collection depends on consent and the application's implementation.
SensorsWhat does the work.
Journeys
It coordinates seller activation using identity, catalogue and listing events supplied by the marketplace.
Localization
It manages Arabic and English buyer or seller content, marks the Arabic locale right-to-left for the host app to render, and handles locale-specific variants.
Messaging Channels
It routes approved order notices through configured providers after the marketplace supplies the relevant event.
Sensors
In preview, it can collect consent-aware runtime signals from remotely activated strings for downstream use.
Residency, certification and integration.
Data residency. Today ContentFlow runs as a single deployment on infrastructure located in Riyadh, Saudi Arabia, so production content and end-user data are processed in the Kingdom; that is a property of how we are currently deployed rather than a control the product enforces, encrypted backups and some third-party processors are handled outside the Kingdom, and an in-Kingdom-only arrangement is something we agree in writing on an Enterprise plan rather than something this page can promise.
Certifications. Our controls are built around the requirements of the Saudi PDPL. Backups are encrypted with AES-256 and restore-tested. HTTPS is enforced across the site. SOC 2 Type II and ISO 27001 are planned.
Production integration today uses the REST API. Native SDKs for React Native, iOS, Android and Web are in preview and are not generally available. The @contentflow/cli package is not published yet.
One engineering integration up front. After that your team publishes content changes without a new app build and without a new app store submission.
What teams ask.
Can seller guidance react to activation events?
Yes. Journeys can advance when the marketplace supplies events for identity checks, catalogue setup or listing preparation.
Can order notices use our existing provider?
Messaging Channels routes approved content through configured providers, subject to supported channel coverage, recipient eligibility and supplied consent data.
Are Sensors generally available?
No. Sensors is in preview behind a feature flag, and native SDKs are also in preview. Current integration is through the REST API.
Five sectors, one platform.
Production integration today uses the REST API. Native SDKs for React Native, iOS, Android and Web are in preview and are not generally available. The @contentflow/cli package is not published yet.