Capability sheet
Oracle Simphony and Dojo360
What the Oracle Simphony connector can read and write, how it authenticates, and the limits to plan around.
- Status
- BetaDocs reviewed · Last reviewed 2026-10-20
- Categories
- Point of Sale
- Industries
- Retail & e-commerce, Hotels, restaurants & hospitality groups, Fuel & convenience retail, Travel & tourism, Healthcare providers
- Regions
- GCC, India, Singapore, Malaysia, US, UK, EU & ANZ
- API and auth
- REST API · OAuth 2.0
- Dojo360 can pull
- Orders
- Items
- Branches
- Payments
- Dojo360 can push
- Items
- Customers
- Webhooks
- Yes
- Sandbox
- Available
- Key limits
- Transaction API access is enabled per enterprise by Oracle.
- Historical order backfill windows vary by POS provider.
- Access requirements
- Admin access to the client account to authorize the connection.
- Plan or partner requirements to be confirmed with the vendor during onboarding.
Oracle Simphony is a trademark of its owner and is used here for identification only. See third-party trademarks.
Stop running six islands
Ready to run it as one operation?
Start with a fixed-price Blueprint. We map every system you run, where work is done twice, and what your Dojo connects first.
Works with the systems you already run