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. 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.
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.
Map the old integration’s intent
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 to record the acceptance criteria. 
