Platform implementation

Stibo STEP

We implement Stibo STEP as the one place where product data is created, enriched in Arabic and English, approved and published to every sales channel.

Man in a kandura and ghutra working at two monitors by a large window

For retailers, distributors and manufacturers, STEP work centres on the product data model: hierarchies, attributes, lists of values and the digital assets attached to each item. Product content in the Gulf usually has to exist in Arabic and English, and local labelling requirements often decide which attributes are mandatory for food and consumer goods. STEP can run as Stibo's SaaS or on infrastructure you control.

Configuration happens in STEP Workbench and the Web UI: the data model, business rules written in JavaScript, and workflows that carry a new item from supplier onboarding through enrichment to approval. Inbound and outbound integration endpoints connect ERP, e-commerce and marketplaces, while digital asset management keeps images and documents with the product.

Stibo STEP and related product names may be trademarks of their respective owners.

How we implement Stibo STEP

From blueprint to go-live and beyond: configuration, integration and support from one accountable team.

  • Blueprint and governance

    The product hierarchy, the attribute dictionary, completeness rules for each channel and the enrichment workflow are agreed with category managers, e-commerce and the product data owner before configuration.

  • Supplier onboarding

    Templates or a portal for new items, with validation that rejects incomplete data before it reaches the category team.

  • Channel syndication

    Channel-specific outputs to your own site, marketplaces and retailer feeds such as GDSN, each with its own completeness check.

  • Bilingual content workflow

    Arabic and English descriptions held as language contexts, with translation tasks, review and approval inside the same workflow.

  • Hypercare and managed support

    Stibo issues regular STEP updates, so we test business rules and integrations against each one, and watch workflow backlogs, failed exports and completeness scores by channel.

When product data needs Stibo STEP

STEP suits retailers, distributors and manufacturers with large catalogues and many channels that need to manage product, supplier and location data on one platform.

  • A catalogue that has outgrown spreadsheets and ERP fields
  • Several channels, each with its own content rules
  • Category managers who will own enrichment
  • Agreement on who translates and approves Arabic content

Plan Stibo STEP with Hosn Al Tomoh

Tell us what the platform needs to do and when. We will propose a first phase with scope, team and an itemised quotation.

Request a phased plan