Manage non-room inventory items (retail, package components, POS-linked items) via the OPERA Cloud Inventory API through OHIP
domain: docs.oracle.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate to OHIP and confirm inventory item management is licensed for the property
Query the property's inventory item master list to see existing SKUs, categories, and pricing
Create or update inventory items with identifiers, price, and category
Map inventory items to packages or point-of-sale elements as required by the business use case
Re-query after changes to confirm the item list reflects the update before it is used in postings
Known gotchas
Inventory items are distinct from room-type/unit inventory (used for availability) and from cashiering item codes used for folio postings; confusing the three modules produces requests against the wrong endpoint
Item master changes may not take effect for in-flight reservations or open folios until the next relevant transaction
Detailed field-level payload requirements are only in the versioned JSON specs on the oracle/hospitality-api-docs GitHub repo, not in the narrative docs.oracle.com pages
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?