Hospitality integration

Mandarin Oriental EDI integration

How EDI and API integration with Mandarin Oriental typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with Mandarin Oriental.

At a glance

Mandarin Oriental integration, in three pictures

The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific Mandarin Oriental program or a customer relationship.

Illustration of a hotel building with a palm tree, representing the hospitality industry that Mandarin Oriental operates in.
Industry. Hospitality: where Mandarin Oriental operates.
Workflow diagram: your ERP and warehouse systems exchange documents with Mandarin Oriental through ECOM. You send 855, 856, 810, 832; you receive 850, 820; 997 acknowledgments go both ways. Your systems ERP · warehouse · finance ECOM integration map · validate · connect · monitor Mandarin Oriental 855 856 810 832 855 856 810 832 850 820 850 820 997 both ways
Workflow. Documents in each direction. Orange: you send. Blue: you receive. Typical, not confirmed.
Comparison diagram: without integration, documents are re-keyed, files are emailed and rejections are found late; with ECOM, documents are mapped to your ERP, validated and monitored, and exceptions are visible early. Without integration Orders re-keyed by hand Files emailed or uploaded Rejections found late With ECOM Documents mapped to your ERP Every file validated and monitored Exceptions visible early
Outcome. From manual handling to a monitored flow. No figures: results depend on your setup.

Talk to an EDI/API Expert about Mandarin Oriental

Tell us which documents you exchange with Mandarin Oriental, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with Mandarin Oriental.

  • Review of Mandarin Oriental's requirements with you, once you have them
  • EDI and API integration with your ERP and warehouse systems
  • Monitoring and managed service after go-live, if you want it

Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.

Takes about 30 seconds. Phone and note are optional.

Your request is about

Trading partner
Mandarin Oriental

When should we talk?

Times are in your time zone. We use this to schedule the conversation.

We use your details only to respond to your request. See our privacy notice. Prefer to talk? Call Sales at 972-836-7750.

Integration and onboarding

How Mandarin Oriental integration fits your systems

Your systemsERP, WMS and accounting
ECOMMapping, validation, connectivity and monitoringAS2 or SFTP · EDI network (VAN) · API or web portal
Mandarin OrientalIts program, documents and requirements
  1. ConfirmConfirm your Mandarin Oriental program, role and the documents it requires.
  2. MapMap each document to your ERP fields and business rules.
  3. ConnectConfigure the connection and security the program needs.
  4. TestTest against the applicable specifications and acknowledgments.
  5. Go liveGo live with monitoring, alerts and exception handling.
Typical implementation path. Exact requirements are confirmed against the applicable specifications during onboarding.

Overview

Understanding Mandarin Oriental integration

Who this is for: Suppliers of food, linens, furniture, amenities and operating supplies that serve Mandarin Oriental, and their order and finance teams.

Scope: This guide describes typical practice for this kind of trading relationship; Mandarin Oriental's own program details are confirmed during onboarding.

Mandarin Oriental is a luxury hotel company. ECOM's directory lists it under luxury hotels. Suppliers to hotels and resorts typically deal with purchase orders from many properties, central catalogs, delivery to individual properties and consolidated invoicing.

What matters most with a hotel or lodging company is that documents reflect what physically happened, and that exceptions are noticed early. Mandarin Oriental's own EDI or API specification is not part of this guide and no Mandarin Oriental document was read: treat what follows as typical practice for a hotel or lodging company, and confirm the documents, X12 version, delivery method and testing steps with Mandarin Oriental.

ECOM maps the documents to your ERP and warehouse systems, tests them with the trading partner, monitors every file after go-live and handles partner changes, as software, as a managed service or both.

Business scenarios

Where Mandarin Oriental integration gets complicated

Typical requirements—confirm with your trading partner.

Many properties, one program

Orders from many properties follow central pricing but ship to separate addresses with their own receiving rules.

How ECOM helps: ECOM maps inventory and stock data between your systems and Mandarin Oriental, so one position reaches every system, with differences listed for review.

What you gain: Stock positions stay consistent, and mismatches are visible early.

Opening and renovation projects

Projects create large, one-time orders with detailed item lists.

How ECOM helps: ECOM runs onboarding as a project: we confirm Mandarin Oriental's requirements with you, map the documents, build the connection and run test cycles until Mandarin Oriental accepts them.

What you gain: A shorter, more predictable path to the first accepted live document.

Many properties, central programs

Hotel programs buy centrally but deliver to individual properties with their own receiving rules and consolidated billing.

How ECOM helps: ECOM maps invoice, payment and remittance data to your ERP or finance system and matches each document to the order or shipment it relates to, with differences listed for review.

What you gain: Faster reconciliation and cash application, and a clear trail for audit.

Seasonal demand

Seasons change order volumes and delivery windows.

How ECOM helps: ECOM runs the connection as a monitored service and watches queues and acknowledgments through busy periods, so a spike does not leave documents waiting.

What you gain: Busy periods run on the same process, without manual catch-up.

Workflows

Typical Mandarin Oriental business workflows

Typical requirements—confirm with your trading partner. Typical flows in this industry, not Mandarin Oriental's published process.

Order to cash

  1. 1Receive 850 purchase order
  2. 2Send 855 acknowledgment
  3. 3Ship and send 856
  4. 4Send 810 invoice

Catalog and price update

  1. 1Prepare item and price data
  2. 2Send 832 update
  3. 3Confirm with 997
  4. 4Take orders on new data

Documents and APIs

Mandarin Oriental documents by program

General guidance. We could not verify Mandarin Oriental's EDI requirements from a published source, so these are documents commonly exchanged in this industry, not Mandarin Oriental's confirmed requirements. Confirm the list, versions and programs with Mandarin Oriental.

DocumentNameDirectionProgramStatusPurpose
850 Purchase Order From Mandarin Oriental Not stated General guidance Typically carries the order: items, quantities, prices, ship-to locations and requested dates.
855 Purchase Order Acknowledgment To Mandarin Oriental Not stated General guidance Typically confirms an order, or reports changes to quantities, prices or dates.
856 Ship Notice/Manifest To Mandarin Oriental Not stated General guidance Typically tells the receiver what is on each shipment, often with carton or pallet label details.
810 Invoice To Mandarin Oriental Not stated General guidance Typically bills for what shipped, matched against the order.
832 Price/Sales Catalog To Mandarin Oriental Not stated General guidance Typically shares item, price and catalog updates.
820 Payment Order/Remittance Advice From Mandarin Oriental Not stated General guidance Typically carries payment and the remittance detail that ties it to invoices.
997 Functional Acknowledgment Both directions Not stated General guidance Typically confirms that each file was received and could be read.

Connectivity

How companies connect

  • AS2 or SFTP

    Many companies exchange EDI files directly over AS2 or SFTP.

    General guidance

  • EDI network (VAN)

    Many suppliers connect through a value-added network that delivers files to and from the partner and keeps an audit trail.

    General guidance

  • API or web portal

    Some programs use REST or SOAP APIs, a supplier portal or a cloud EDI service for some documents. A login is usually required for portals.

    General guidance

Challenges

Common integration challenges

  • Ship-to variety

    Properties have different receiving rules.

  • Catalog and pricing

    Prices must match the program. Details depend on your agreement with Mandarin Oriental.

  • Project orders

    Large orders need detailed tracking. Ask Mandarin Oriental how this applies to your program.

  • Invoice matching

    Invoices must tie to the property. Requirements vary by program.

  • Program-specific details

    The documents, identifiers, versions and test steps for your program are set by Mandarin Oriental. ECOM works from them during mapping and testing.

Automation options for Mandarin Oriental suppliers

Four ways to automate. One foundation.

ECOM helps you automate them, meet Mandarin Oriental's labeling and ship notice requirements, and see what needs action. Mandarin Oriental sets its program's rules; ECOM confirms which options fit yours.

PRISM Supply Chain Automation Foundation

One platform beneath every option. Use one, or combine them for different partners and documents.

Compliance and actionable visibility

Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.

Discuss Your Trading Partner Requirements

Connect Mandarin Oriental documents to your ERP

ECOM connects the documents you exchange with Mandarin Oriental to your ERP and warehouse systems, so orders post without re-keying and ship notices and invoices come from the data you already hold.

Industry

Hospitality

See how ECOM supports hospitality suppliers and operators.

Solution

Procure-to-Pay Automation

Automate purchase orders, receipts and invoices on the buyer side.

Service

Fully Managed EDI

Have ECOM run your EDI connections, monitoring and partner changes.

General EDI flow

How EDI with Mandarin Oriental typically works

The documents, their order and the timing are Mandarin Oriental's to set; this is the general sequence most programs of this kind follow.

  1. 850 Purchase Order

    From Mandarin Oriental to you

    Typically carries the order: items, quantities, prices, ship-to locations and requested dates.

  2. 855 Purchase Order Acknowledgment

    From you to Mandarin Oriental

    Typically confirms an order, or reports changes to quantities, prices or dates.

  3. 856 Ship Notice/Manifest

    From you to Mandarin Oriental

    Typically tells the receiver what is on each shipment, often with carton or pallet label details.

  4. 810 Invoice

    From you to Mandarin Oriental

    Typically bills for what shipped, matched against the order.

  5. 832 Price/Sales Catalog

    From you to Mandarin Oriental

    Typically shares item, price and catalog updates.

  6. 820 Payment Order/Remittance Advice

    From Mandarin Oriental to you

    Typically carries payment and the remittance detail that ties it to invoices.

  7. 997 Functional Acknowledgment

    Both directions

    Typically confirms that each file was received and could be read.

Need help with the specification?

Tell ECOM which program you are in and what the partner has given you. We help you read it, confirm the applicable requirements, map them to your systems and test against them. Do not send passwords or EDI identifiers with your request.

Next step

Get help with your Mandarin Oriental program

Each request goes to an ECOM EDI specialist with Mandarin Oriental's name attached, so the reply starts from your program.

  • Review Mandarin Oriental's requirements

    Send us Mandarin Oriental's guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect Mandarin Oriental to your ERP

    Orders in, ship notices and invoices out, from the ERP and warehouse systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each Mandarin Oriental document, then go live with monitoring from the first file.

    Plan testing and certification
  • Shipping labels and ASNs

    Labels and ship notices that match Mandarin Oriental's rules, to help avoid receiving problems and compliance deductions.

    Review shipping compliance

Mandarin Oriental integration FAQs

Does Mandarin Oriental use EDI with suppliers?

Hotel companies often buy through procurement platforms or group purchasing programs that may accept EDI or portal orders. This page does not describe Mandarin Oriental's program.

Can ECOM help with orders from many properties?

ECOM maps orders and invoices between a customer's format and your ERP and monitors each file, including orders for many ship-to locations.

Which EDI documents are typical for a hotel or lodging company?

Typical documents are 850, 855, 856, 810, 832, 820, 997. That is general practice, not Mandarin Oriental's published list.

How does onboarding with Mandarin Oriental usually work?

Typically you get the specification from the trading partner, agree the connection, map to your systems, test until the partner accepts the documents, then go live with monitoring. Timing depends on Mandarin Oriental's requirements, test cycles and your ERP.

Does this guide mean Mandarin Oriental endorses ECOM?

No. This is an independent integration guide. It does not indicate an endorsement, partnership or approval by Mandarin Oriental.

Sources and accuracy

This guide summarizes publicly available information as of November 2026. Mandarin Oriental sets its own requirements and can change them at any time; your Mandarin Oriental implementation guide, supplier portal or account contact is the authoritative source for your program.

  • ASC X12: transaction set reference (standards body) Standards reference
  • Mandarin Oriental: company description Background, not checked against a company source The one-sentence description of Mandarin Oriental comes from general public knowledge and was not checked against Mandarin Oriental's own website for this page.
  • Mandarin Oriental: no company document read Background, not checked against a company source No Mandarin Oriental supplier, customer or integration document was read for this page. Everything shown is typical practice for this type of company.

Request Mandarin Oriental integration assistance

Tell us about your Mandarin Oriental program, documents and ERP. We will outline the connection, mapping and testing plan.