Skip to content

Commit d61c1e4

Browse files
authored
Merge branch 'main' into jh_fix-link
2 parents c00f50b + d27a0cb commit d61c1e4

File tree

1 file changed

+26
-0
lines changed

1 file changed

+26
-0
lines changed

src/pages/starter-kit/checkout/tax-use-cases.md

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -204,3 +204,29 @@ Here's an example payload showing how the custom attributes from tax classes app
204204
}
205205
}
206206
```
207+
208+
## Propagate custom attributes of tax classes
209+
210+
The out-of-process tax module introduces support for assigning serialized custom attributes to tax classes. These attributes are then automatically associated with shopping cart data during cart creation and product addition. This allows for tax-related metadata to be included early in the checkout process and carried forward into subsequent operations.
211+
212+
### How it works
213+
214+
- **Customer Tax Class > Quote**:
215+
When a customer creates a shopping cart, any serialized custom attributes associated with the customer's tax class are copied to the `Quote` entity.
216+
217+
- **Product Tax Class > Quote Item**:
218+
When a product is added to the cart, serialized custom attributes from the product's tax class are copied to the corresponding `Quote Item`.
219+
220+
This ensures that both the `Quote` and each `Quote Item` contain tax-relevant custom data for further processing or integration.
221+
222+
### Quote to Order propagation
223+
224+
Once the customer places an order, all serialized custom attributes already present in the `Quote` and `Quote Item` entities are automatically propagated to the `Order` and `Order Item` entities, respectively.
225+
226+
This propagation ensures that tax class metadata—initially attached by customer and product associations—is consistently preserved throughout the entire checkout lifecycle. This allows external systems (such as tax calculation services) to access the tax class and its serialized custom attributes using:
227+
228+
- REST APIs
229+
- GraphQL queries
230+
- Event-driven integrations using Adobe Commerce Eventing
231+
232+
This consistency is critical for third-party integrations that rely on tax classification metadata for compliance, reporting, or invoicing purposes.

0 commit comments

Comments
 (0)