> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stateset.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Commerce Network Orders: Migration Guide

> Move from legacy chain-order examples to a tested local order workflow and explicit integration boundaries.

This URL previously showed order submissions to legacy Commerce Network RPC hosts. Those
commands do not establish a currently provisioned network or a supported client contract.
For a runnable order workflow, use the embedded commerce engine.

## Create and verify an order locally

Follow the [orders quickstart](/guides/orders-quickstart). It creates a customer and inventory,
creates an order with exact decimal prices, checks stock allocation, and tests rejection and
cancellation. Use the returned IDs rather than the illustrative identifiers from old examples.

<Note>
  An embedded order lives in your application’s database. Creating it does not broadcast a
  blockchain transaction, charge a payment provider, or create a shipment.
</Note>

## Map the old integration’s intent

| Previous intent | Current starting point | Verify |
| - | - | - |
| Create an order | [Orders](/guides/orders-quickstart) | Returned ID, amount, currency, and stock allocation |
| Fulfill an order | [Fulfillment](/guides/commerce/fulfillment) | Shipment state and separately verified carrier action |
| Cancel an order | [Order lifecycle](/stateset-icommerce/stateset-icommerce-order-lifecycle) | Valid transition and released allocation |
| Record a payment | [Payments](/guides/payments-quickstart) | Local record plus separate provider result |
| Integrate an existing store | [Connect your operation](/guides/connect-your-operation) | Source of truth and external-ID mapping |

## Existing chain integrations

Retain the chain transaction and original order identifiers when planning a migration. Agree
on a source of truth and a cutover boundary before importing records; do not resubmit historical
orders as new purchases. Obtain the network’s deployed contract from its owner if continuing
to operate it. The embedded and HTTP contracts do not imply wire compatibility with chain messages.

## Finish the migration check

Select one representative order and reconcile its customer, lines, totals, payment evidence,
and fulfillment state in both systems. Repeat with a cancellation and a partial fulfillment.
Use [integration testing](/guides/comprehensive-testing-guide) to record the acceptance criteria.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.