EDI & B2B

Trading-partner data that is validated before it ever leaves your business.

OpenText Business Network is the B2B integration layer many enterprise retailers and suppliers trade across, carrying structured documents between partners. Qooly sits upstream of it as the product data layer: item identity, attributes, imagery and pricing are validated and governed in Qooly first, so the catalog data reaching each trading partner is correct and consistent. The integration is scoped to product data: transactional documents such as purchase orders, invoices and shipping notices stay in OpenText and your ERP, and stock positions stay with the systems that own them.

What syncs

6 of 9

  • Item masters (products)
  • Product attributes and metadata
  • Images and media
  • Pricing by partner
  • Barcodes and item identity
  • Partner-specific data formats
  • Stock and availability (not supported)
  • Purchase orders and invoices (not supported)
  • Shipping notices (ASN) (not supported)

Key capabilities

Correct before it is sent

Item identity, attributes and barcodes are validated against each partner's requirements before data leaves your business, so errors are caught upstream instead of becoming partner exceptions.

Per-partner shaping

Every trading partner wants the same product described differently. Agent Flow maps and transforms one governed record into the shape each partner expects.

Imagery that meets spec

Partner image requirements differ on count, naming and dimensions. Agent Sync delivers the right assets in the right shape alongside the product record.

Partner pricing

Partner-specific price lists are maintained alongside retail pricing, governed by the same approval rules before release.

How to connect

5 steps

  1. 01

    Provision access for Qooly alongside your OpenText Business Network setup

  2. 02

    Map your item, attribute, imagery and price fields to your catalog schema

  3. 03

    Define the data requirements each trading partner must satisfy

  4. 04

    Set the validation rules that must pass before data is released

  5. 05

    Enable scheduled and change-driven sync

Who uses this connector

  • Suppliers trading with large retailers who reject data that misses required attributes
  • Brands keeping one governed product record behind both their sales channels and their partner feeds
  • Teams that want product data errors caught before they become trading-partner exceptions

Common questions

Ready to connect?

Get OpenText live in hours.

No engineering required. Connect your account, map your fields, and your catalog syncs automatically.