Skip to content
EDI Ulta Beauty Ulta Beauty via OpenText

Channel

Ulta BeautyUlta Beauty via OpenText

Ulta Beauty via OpenText is one of Ulta Beauty's 3 EDI trading channels. It supports 6 document types including X12 856, X12 852, X12 850, X12 860, X12 810, and more.

Book a demo ← All Ulta Beauty channels
Documents
6 transactions
Standards
X12 + EDIFACT
Transport
AS2 · SFTP · API

Document catalog

EDI documents we support for Ulta Beauty Ulta Beauty via OpenText

6 EDI transactions ready to integrate.

Document flow on this channel

How documents flow on Ulta Beauty via OpenText

This channel carries all 6 of Ulta Beauty's document types.

Catalog & inventory

Partial on this channel
  1. 832 Price / Sales Catalog not on Ulta Beauty via OpenText
  2. 846 Inventory Inquiry / Advice not on Ulta Beauty via OpenText
  3. 852 Product Activity Data

Network onboarding

Ulta Beauty via OpenText is routed through OpenText

Stacksync maintains a certified OpenText connection covering 3 trading partners across 3 channels. Onboarding with Ulta Beauty on this channel reuses that connection — no separate VAN contract or certification cycle.

OpenText Trading Grid is the EDI messaging service of OpenText Business Network, which OpenText describes as the world's largest business network. Large buying organizations across retail, automotive, and logistics route purchase orders, invoices, ship notices, and transportation documents through it, and suppliers connect via a network mailbox or a direct connection. Documents follow ANSI X12 and EDIFACT standards, with both self-service and fully managed onboarding options.

Connecting via OpenText
  1. Set up a Trading Grid account, either directly with OpenText or through the buying organization's supplier-enablement program, and complete the service agreement.
  2. Establish connectivity: a Trading Grid mailbox or a direct AS2, SFTP, FTPS, or HTTPS connection. AS2 setups include exchanging IDs and signing and encryption certificates with the Trading Grid Messaging Service (TGMS).
  3. Map documents to the buyer's ANSI X12 or EDIFACT implementation guides, using self-service tooling or OpenText managed services.
  4. Run the buyer's test cycle over the network and verify transaction processing and delivery before production cutover.

Testing: There is no single network-wide certification; testing follows the buying organization's implementation guides and test plan. Connectivity is validated first (for AS2, certificate exchange with the Trading Grid Messaging Service), then document-level tests run with each trading partner. OpenText notices also expect partners to verify transaction processing and delivery after connectivity or certificate changes.

Timeline: No standard public timeline. OpenText cites a retail customer onboarding international vendors in as little as five working days; direct ERP-integrated connections typically take longer and are paced by the buying organization's test plan.

Most-traded documents on OpenText
  • 810 2 ch
  • 850 2 ch
  • 856 2 ch
  • 860 2 ch
  • 204 1 ch
  • 210 1 ch
Other partners reachable via OpenText

Trading partners

2+ trading partners.
And every channel covered.

We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.

Browse the full directory

Ready to automate your Ulta Beauty EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.

Book a Ulta Beauty EDI demo Tour the platform on your own