Source
Order operations & back office — found from sitemap — VTEX
Checked for VTEX on 10 Nov 2026
- Page
- https://developers.vtex.com/docs/guides/change-orders-multilevel-omnichannel-inventory-external-marketplaces
- Checked
- 10 Nov 2026, 06:46 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:34e98be1e4f3f84e906b5a7cbd6aa47bbe0dd8818d8cb32c534d547c43714dec
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Moi definition Report an error
“Multilevel Omnichannel Inventory is the VTEX setting that allows franchise accounts or white label sellers' inventory to be sold in marketplaces connected to the main account.”
-
Change order item price change Report an error
“By configuring this feature, your VTEX store will be able to have orders' items or prices changed when selling products that belong to a franchise account in orders made in external marketplaces.”
-
Implementers Report an error
“The integration can be implemented by: Integration partner with the technical ability to implement integrations. External marketplace who develops an integration with a VTEX store.”
-
Oms payment requirement Report an error
“The external marketplace must be responsible for the payment process, otherwise the change order in Multilevel Omnichannel Inventory chain orders in external marketplaces operations will be blocked by the Order Management System (OMS).”
-
Change notification endpoint Report an error
“The endpoint must have a base URL followed by /pvt/orders/{orderGroup}/changes .”
-
Marketplace services endpoint field Report an error
“The external marketplace informs the base URL to VTEX's Order Management System (OMS) when a new order is placed in the external marketplace, by using the marketplaceServicesEndpoint field in the Order placement API.”
-
Change payload same as register change API Report an error
“The payload sent to the external marketplace follows the same structure used in the Register change on order API.”
-
Change payload fields Report an error
“reason string Text explaining why there was a change in the order. This information may be shown to the shopper in the storefront or transactional emails. discountValue integer This field can be used to apply a discount to the total value of the order. Value in cents. incrementValue integer This field can be used to increment the total value of the order. Value in cents.”
-
Change item fields Report an error
“sellerItemId string SKU ID of the item to be added to the order. quantity integer Quantity of items to be added to the order. price integer Total amount in cents of the item to be added to the order. unitMultiplier integer Unit multiplier of the item to be added to the order. measurementUnit string Item's measurement unit.”
-
Change response success Report an error
“Response 200 OK: confirmation and payload as the following example”
-
Change response error Report an error
“Response 500 error: message of failure and there is no payload.”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The B2B Seller Order operations & back office
- The Data Protection Officer Order operations & back office
- The Developer Order operations & back office
- The Merchant Catalogue & checkout
- The Merchant Order operations & back office
- The Operations Lead Order operations & back office
- The Skeptic Order operations & back office