Examples of Standard Transaction & Transaction Item Feeds¶

In the examples below, only the relevant feeds and relevant lines will be shown. Additionally, only the relevant columns will be shown, and for better clarity, this may or may not include all “required” columns from the feeds. Please refer to the documentation specific to each feed in case you have a doubt about which columns are actually required.

Use case #1¶

Order placed on Day 0, one product is canceled on Day 1, one product is shipped on Day 2

The transaction feed doesn’t need to be updated (since neither the customer nor the date of the initial transaction changed). However, the transaction item needs to reflect those changes. Note that those changes will be represented incrementally (ie only the new/updated lines will be shown) : you can provide either the increment as shown in each case or provide a full history every time, but you should follow the same conventions regardless.

Feed: TransactionItem

Day 0

SourceTransactionItemNumber	SourceTransactionNumber	Type	SubType	InvoiceDate	ShipDate	SaleRevenue	SourceProductNumber	Quantity	DateCreated
ABC1-Demand	ABC	Purchase	Demand	Day0		10	P1	1	Day0
ABC2-Demand	ABC	Purchase	Demand	Day0		30	P2	1	Day0

Day 1

SourceTransactionItemNumber	SourceTransactionNumber	Type	SubType	InvoiceDate	ShipDate	SaleRevenue	SourceProductNumber	Quantity	DateCreated
ABC1-Canceled	ABC	Purchase	Canceled	Day0	Day1	-10	P1	-1	Day1

Day 2

SourceTransactionItemNumber	SourceTransactionNumber	Type	SubType	InvoiceDate	ShipDate	SaleRevenue	SourceProductNumber	Quantity	DateCreated
ABC2-Shipped	ABC	Purchase	Shipped	Day0	Day2	30	P2	1	Day2

Use case #2¶

Order placed on Day 0, all products are shipped on Day 1, one product has a discount of $10, the whole order has a $5 discount and one product is returned on Day2

The transaction-level discount will be spread evenly between the two items in the transaction in this example, but you can imagine spreading them based on a the relative price of each item, or other means.