Database

Store and query operational data with SyncMyOrders object models instead of wiring your own tables.

SyncMyOrders includes a built-in database for operational data like orders, customers, and job metadata. Define schemas, persist records from scenarios, and read them back without managing external storage.

When to use it

• Keep a normalized catalog of orders or shipments that multiple scenarios can reference.
• Track state between runs (deduplication keys, pagination cursors, reconciliation checkpoints).
• Cache enrichment results so you don’t re-call third-party APIs unnecessarily.
• Prototype quickly without setting up a separate database or ORM.

Core pieces

• Schemas: Define the fields and types your scenarios will write (for example, order_id, channel, status, total).
• Instances: Records created from a schema, written and read via the Object Model agent.
• Queries: Filters to fetch slices of data for downstream processing or reporting.

Getting started

1. Model the object you need (orders, shipments, customers, or a custom helper object).
2. Create or update the schema with required fields and validation where possible.
3. Use the Object Model agent in your scenario steps to create, query, or update records.
4. Keep indexes lean and fields purposeful to avoid storing unnecessary payloads.