Skip to content

Commit aae0c93

Browse files
author
Jo
committed
first draft
1 parent b50a59c commit aae0c93

File tree

9 files changed

+20
-14
lines changed

9 files changed

+20
-14
lines changed

docs/partials/inventory/overview.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ Inventory is the quantity of each product that you have in stock. The inventory
55
You can manage inventory using both:
66

77
- the [Inventories API](/docs/api/pxm/inventory)
8-
- [Commerce Manager](/docs/commerce-manager/product-experience-manager/Products/manage-product-inventory).
8+
- [Commerce Manager](/docs/commerce-manager/product-experience-manager/Products/manage-product-inventory)
99

1010
### What is Inventory?
1111

docs/partials/inventory/unpaidorder.mdx

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,10 @@ The following flowchart shows the process for an unpaid order.
66
Stock is managed as follows:
77

88
1. When a customer attempts to add products to a cart, the inventory service checks if there is enough available stock. If there is not enough stock available, you receive a 400 HTTP response with a warning. The response does not describe what products cannot be added, nor does it return how many products are in stock.
9-
2. If a customer successfully adds products to a cart, the customer can checkout to create an unpaid order.
10-
3. A final check on the available stock is performed.
11-
4. After creating the unpaid order, the payment for an order can be taken. When a customer attempts to pay for an order, the inventory service reserves the stock before the payment is processed internally. At any time before the point of payment, a customer might lose their order, if the customer is slower than everyone else.
12-
5. If the payment fails, the temporary stock allocation is removed, and the stock becomes available again for anyone to buy.
9+
1. If a customer successfully adds products to a cart, the customer can optionally choose the location of the stock (if this order is for collection).
10+
1. The inventory service checks if there is enough available stock at the location.
11+
1. If there is enough stock available at the location, then the customer can checkout to create an unpaid order.
12+
1. A final check on the available stock is performed.
13+
1. After creating the unpaid order, the payment for an order can be taken. When a customer attempts to pay for an order, the inventory service reserves the stock before the payment is processed internally. At any time before the point of payment, a customer might lose their order, if the customer is slower than everyone else.
14+
1. If the payment fails, the temporary stock allocation is removed, and the stock becomes available again for anyone to buy.
1315

guides/key-concepts/inventory/characteristcs.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Characteristics
3-
nav_label: Characteristics
2+
title: Inventory Characteristics
3+
nav_label: Inventory Characteristics
44
sidebar_position: 30
55
---
66

guides/key-concepts/inventory/transactions.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Transactions
3-
nav_label: Transactions
2+
title: Inventory Transactions
3+
nav_label: Inventory Transactions
44
sidebar_position: 20
55
---
66

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
{
22
"position": 25,
3-
"label": "Workflow",
3+
"label": "Inventory Workflow",
44
"collapsible": true
55
}

guides/key-concepts/inventory/workflow/paidorder.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Paid Order Flow
33
nav_label: Paid Order Flow
4-
sidebar_position: 10
4+
sidebar_position: 15
55
---
66

77
import PaidOrder from "/docs/partials/inventory/paidorder.mdx";
Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,11 @@
11
---
22
title: Unpaid Order Flow
33
nav_label: Unpaid Order Flow
4-
sidebar_position: 15
4+
sidebar_position: 10
55
---
66

77
import UnpaidOrder from "/docs/partials/inventory/unpaidorder.mdx";
88

99
<UnpaidOrder></UnpaidOrder>
10+
11+
Once payment is completed, the order transitions to a [paid order](/guides/key-concepts/inventory/workflow/paidorder), allowing further processing, such as fulfillment or shipping.
Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,11 @@
11
---
2-
title: Overview
3-
nav_label: Overview
2+
title: Inventory Workflow
3+
nav_label: Inventory Workflow
44
sidebar_position: 5
55
---
66

77
import InventoryWorkflow from "/docs/partials/inventory/workflow.mdx";
88

99
<InventoryWorkflow></InventoryWorkflow>
10+
11+
The order service first creates an [unpaid order](/guides/key-concepts/inventory/workflow/unpaidorder), which records the order details and holds the items. Once payment is completed, the order transitions to a [paid order](/guides/key-concepts/inventory/workflow/paidorder), allowing further processing, such as fulfillment or shipping.

static/assets/unpaidorder.png

3.74 KB
Loading

0 commit comments

Comments
 (0)