Legend
Serialized Exception: Scenario 1-1A: Overage – Discovered at Receiving (Keep)
Seller Serialization Data Management
System
Seller
S0: Seller has serialized
Inventory On Hand
Create
Commissioning
Event objects
(E1)
trigger
E1i2
(LSU2)
Buyer Serialization Data Management
System
...
E1in
(LSU n)
E2: Packing Events
E2[c-i]1
(case 1)
E2[c-i]2
(case 2)
...
E2[c-i]n
(case n)
LSU – Lowest Saleable Unit
E1c1
E1c2
E1cn
(case 1)
(case 2)
(case n)
S1: Buyer places order
for two cases
...
S3: Seller ships three
physical cases by
mistake. IT systems
think only 2 cases have
been shipped.
O2
O1
S2: Seller processes
order for two cases
read
Create Shipping
Event object
(E3)
Get relevant
Commissioning
event objects
(E1)
read
*redacted to include only SNs 123 and 456
Get relevant
Packing event
objects (E2)
send
E1*:
Commissioning
Events (case
SNs 123, 456)
E2: Packing
Events (case SNs
123, 456)
E3: Shipping
Event (case SNs
123, 456)
Process incoming
Commissioning,
Packing, Shipping
Events
Verify scanned
physical goods
against Seller
events
S4: Three cases arrive
at buyer’s dock
SN 123, 456, 789
create
E3: Shipping
Event (case SNs
123, 456)
Create
Receiving Event
object (E4)
E4: Receiving
Event (case SNs
123, 456)
S5: Buyer receives SN
123, 456, but cannot
receive 789 because
there is no data
S6: Buyer quarantines
case 789 because
there is no data
Situational: Cases are opened before put-away
Unpack cases
S7: Buyer notifies
seller of overage
E5: Unpacking
Event (case SNs
123, 456)
O1
read
S8: Seller investigates
discrepancy for case SN 789,
and determines SN 789 is
shipped by mistake. Seller
creates a shipping event to
reflect the prior shipment
Create Shipping
Event object
(E6)
Get relevant
Commissioning
event objects
(E1)
O2
read
Get relevant
Packing event
objects (E2)
Note: Read from previously created events
*redacted to include only SN 789
send
E1*:
Commissioning
Events
(case SN 789)
E2: Packing
Event
(case SN 789)
E6: Shipping
Event
(case SN 789)
Process incoming
Commissioning,
Packing, Shipping
Events
Verify scanned
physical goods
against Seller
events
create
E6: Shipping
Event (case SN
789)
Event
Object
Buyer
create
E1: Commissioning Events
E1i1
(LSU1)
Network Exchange
Create Packing
Event objects
(E2)
create
S1
Business
Step
Create
Receiving Event
object (E7)
E7: Receiving
Event (case SN
789)
Situational: Cases are opened before put-away
Unpack case
E8: Unpacking
Event (case SN
789)
S9: Buyer now receives
case SN 789
S1
System
Process
Step
Connector
Data Interface
Legend
Serialized Exception: Scenario 1-1B: Overage – Discovered at Receiving (Refuse/Return)
Seller Serialization Data Management
System
Seller
S0: Seller has serialized
Inventory On Hand
Create
Commissioning
Event objects
(E1)
trigger
E1i2
(LSU2)
...
Buyer Serialization Data Management
System
E1in
(LSU n)
E2: Packing Events
E2[c-i]1
(case 1)
E2[c-i]2
(case 2)
...
E2[c-i]n
(case n)
LSU – Lowest Saleable Unit
E1c1
E1c2
E1cn
(case 1)
(case 2)
(case n)
S1: Buyer places order
for two cases
...
S3: Seller ships three
physical cases by
mistake. IT systems
think only 2 cases have
been shipped.
read
Create Shipping
Event object
(E3)
Get relevant
Commissioning
event objects
(E1)
read
*redacted to include only SNs 123 and 456
Get relevant
Packing event
objects (E2)
send
E1*:
Commissioning
Events (case
SNs 123, 456)
E2: Packing
Events (case SNs
123, 456)
E3: Shipping
Event (case SNs
123, 456)
Process incoming
Commissioning,
Packing, Shipping
Events
Verify scanned
physical goods
against Seller
events
S4: Three cases arrive
at buyer’s dock
SN 123, 456, 789
create
E3: Shipping
Event (case SNs
123, 456)
Create
Receiving Event
object (E4)
S5: Buyer receives SN
123, 456, but cannot
receive 789 because
there is no data
Refuse
E4: Receiving
Event (case SNs
123, 456)
Return
Situational: Cases are opened before put-away
Unpack cases
E5: Unpacking
Event (case SNs
123, 456)
S8: Seller investigates
discrepancy for case SN 789,
and determines SN 789 is
shipped by mistake.
S9: Seller receives back case
SN 789 from the buyer.
S1
O2
O1
S2: Seller processes
order for two cases
Event
Object
Buyer
create
E1: Commissioning Events
E1i1
(LSU1)
Network Exchange
Create Packing
Event objects
(E2)
create
S1
Business
Step
S6b: Buyer quarantines
case SN 789 and
subsequently returns
case SN 789 to seller
because there is no data
S7: Buyer notifies seller of
overage and informs
seller of the buyer’s
decision to either refuse
or return case SN 789.
S6a: Buyer refuses to
receive case SN 789
from carrier because
there is no data.
System
Process
Step
Connector
Data Interface
Legend
Scenario 1-2: Traceability data contains incorrect lot information for entire shipment
Seller Serialization Data Management
System
Seller
S0: Seller has serialized
Inventory On Hand
trigger
Create
Commissioning
Event objects
(E1)
Network Exchange
Buyer Serialization Data Management
System
create
E1: Commissioning Events
E1in
E1i1
E1i2
(LSU n)
(LSU1)
(LSU2)
LSU – Lowest Saleable Unit
E1c1
E1c2
E1cn
(case 1)
(case 2)
(case n)
...
E2: Packing Events
E2[c-i]1
(case 1)
E2[c-i]2
(case 2)
...
E2[c-i]n
(case n)
S1: Buyer places order
for two cases
...
S2: Seller processes
order for two cases
S3: Seller ships two
cases from Lot# XYZ.
IT system incorrectly
thinks both cases are
from Lot# ABC.
S1
O1
read
Create Shipping
Event object
(E3)
Get relevant
Commissioning
event objects
(E1)
read
*redacted to include only SNs 123 and 456
Get relevant
Packing event
objects (E2)
send
E1*: Commissioning
Events (case SNs 123,
456) Lot # ABC
E2: Packing Events
(case SNs 123, 456)
E3: Shipping Event
(case SNs 123, 456)
Process incoming
Commissioning,
Packing, Shipping
Events
Verify scanned
physical goods
against Seller
events
S4: Two cases arrive at
buyer’s dock
SN 123, 456. Both are
from Lot #XYZ.
create
E3: Shipping
Event (case SNs
123, 456)
S5: Buyer quarantines cases
123 and 456 because Lot#
ABC in Commissioning
events do NOT match Lot#
XYZ in the physical products.
S6: Buyer notifies
seller of incorrect lot
data in EPCIS
Commissioning events.
S7: Seller investigates lot
discrepancy. Seller
determines case SNs 123 and
456 are legitimate but the
incorrect lot was recorded.
Seller rectifies incorrect
commissioning events.
Event
Object
Buyer
Create Packing
Event objects
(E2)
create
S1
Business
Step
Create
Commissioning
event
errorDeclaration
objects (E4)
E4: Commissioning
event
errorDeclaration
(case SN 123, 456 )
Lot # ABC
Create
commissioning
event objects
(E5)
E5: Commissioning
Events (case SN 123,
456)
Lot # XYZ
send
E4: Commissioning
event
errorDeclaration
(case SN 123, 456 )
Lot # ABC
E5: Commissioning
Events (case SNs 123,
456) Lot # XYZ
Process incoming
Commissioning
Events
Verify scanned
physical goods
against Seller
events
Create
Receiving Event
object (E6)
E6: Receiving
Event (case SN
123, 456)
Situational: Cases are opened before put-away
Unpack cases
E7: Unpacking
Event (case SNs
123, 456)
S8: Buyer now receives
case SN 123, 456
System
Process
Step
Connector
Data Interface
Legend
Serialized Exception: Scenario 1-3A: Quantity Inference Concealed Overage (Keep)
Seller Serialization Data Management
System
Seller
S0: Seller has serialized
Inventory On Hand
Create
Commissioning
Event objects
(E1)
trigger
E1i2
(LSU2)
...
Buyer Serialization Data Management
System
E1in
(LSU n)
E2: Packing Events
E2[c-i]1
(case 1)
E2[c-i]2
(case 2)
...
E2[c-i]n
(case n)
LSU – Lowest Saleable Unit
E1c1
E1c2
E1cn
(case 1)
(case 2)
(case n)
S1: Buyer places order
for one case
...
S2: Seller processes
order for one case
S3: Seller physically
ships one case thinking
there are twelve
serialized lowest
saleable units in the
case.
O2
O1
read
read
Create Shipping
Event object
(E3)
Get relevant
Commissioning
event objects
(E1)
*redacted to include only SNs 123
Get relevant
Packing event
objects (E2)
send
E1*:
Commissioning
Events (case
SNs 123)
E2: Packing
Events (case SN
123)
E3: Shipping
Event (case SN
123)
Process incoming
Commissioning,
Packing, Shipping
Events
Verify scanned
physical goods
against Seller
events
S4: One case arrives at
buyer’s dock
SN 123
create
E3: Shipping
Event (case SN
123)
Create
Receiving Event
object (E4)
S5: Buyer receives SN
123
E4: Receiving
Event (case SN
123)
Unpack case
Verify scanned
physical goods
against Seller
events
E5: Unpacking
Event (case SN
123)
S6: Buyer opens up
case SN 123 and
discovers there are
thirteen SNs inside.
S7: Buyer quarantines
extra lowest saleable
unit SN 112 because
there is no data.
S8: Buyer notifies
seller of overage
O1
read
S9: Seller investigates SN 112,
the extra serialized lowest
saleable unit found inside case
SN 123. Seller determines SN
112 is shipped by mistake.
Seller generates shipment
message so buyer can keep SN
112.
Create Shipping
Event object
(E6)
Get relevant
Commissioning
event objects
(E1)
Note: Read from previously created events
*redacted to include only SN 112
send
E1*:
Commissioning
Event
(lowest saleable
unit SN 112)
E6: Shipping Event
(lowest saleable
unit SN 112)
Process incoming
Commissioning
and Shipping
Events
Verify scanned
physical goods
against Seller
events
create
E6: Shipping
Event (lowest
saleable unit SN
112)
Event
Object
Buyer
create
E1: Commissioning Events
E1i1
(LSU1)
Network Exchange
Create Packing
Event objects
(E2)
create
S1
Business
Step
Create
Receiving Event
object (E7)
E7: Receiving
Event (lowest
saleable unit SN
112)
S10: Buyer now
receives lowest
saleable unit SN 112
S1
System
Process
Step
Connector
Data Interface
Legend
Serialized Exception: Scenario 1-3B: Quantity Inference Concealed Overage (Return)
Seller Serialization Data Management
System
Seller
S0: Seller has serialized
Inventory On Hand
Create
Commissioning
Event objects
(E1)
trigger
E1i2
(LSU2)
...
Buyer Serialization Data Management
System
E1in
(LSU n)
E2: Packing Events
E2[c-i]1
(case 1)
E2[c-i]2
(case 2)
...
E2[c-i]n
(case n)
LSU – Lowest Saleable Unit
E1c1
E1c2
E1cn
(case 1)
(case 2)
(case n)
S1: Buyer places order
for one case
...
S2: Seller processes
order for one case
S3: Seller physically
ships one case thinking
there are twelve
serialized lowest
saleable units in the
case.
O2
O1
read
Create Shipping
Event object
(E3)
Get relevant
Commissioning
event objects
(E1)
read
*redacted to include only SNs 123
Get relevant
Packing event
objects (E2)
send
E1*:
Commissioning
Events (case
SNs 123)
E2: Packing
Events (case SN
123)
E3: Shipping
Event (case SN
123)
Process incoming
Commissioning,
Packing, Shipping
Events
Verify scanned
physical goods
against Seller
events
S4: One case arrives at
buyer’s dock
SN 123
create
E3: Shipping
Event (case SN
123)
Create
Receiving Event
object (E4)
S5: Buyer receives SN
123
E4: Receiving
Event (case SN
123)
Unpack case
E5: Unpacking
Event (case SN
123)
Verify scanned
physical goods
against Seller
events
S6: Buyer opens up
case SN 123 and
discovers there are
thirteen SNs inside.
S7: Buyer quarantines
extra lowest saleable
unit SN 112 because
there is no data.
S8: Buyer notifies
seller of overage and
returns extra lowest
saleable unit SN 112
S9: Seller investigates SN 112,
the extra serialized lowest
saleable unit found inside case
SN 123. Seller determines SN
112 is shipped by mistake.
S10: Seller receives back
case SN 789 from the buyer.
Event
Object
Buyer
create
E1: Commissioning Events
E1i1
(LSU1)
Network Exchange
Create Packing
Event objects
(E2)
create
S1
Business
Step
S1
System
Process
Step
Connector
Data Interface
Legend
Serialized Exception: Scenario 1-4A: Traceability contains data incorrect serial number in Shipping event
Seller Serialization Data Management
System
Seller
S0: Seller has serialized
Inventory On Hand
Create
Commissioning
Event objects
(E1)
trigger
E1i2
(LSU2)
...
E1in
(LSU n)
E2: Packing Events
E2[c-i]1
(case 1)
E2[c-i]2
(case 2)
...
E2[c-i]n
(case n)
LSU – Lowest Saleable Unit
E1c1
E1c2
E1cn
(case 1)
(case 2)
(case n)
S1: Buyer places order
for three cases
...
S3: Seller ships three
physical cases SN 123, 456,
and 789. IT system
mistakenly records shipping
case SN 891 instead of SN
789.
O2
O1
S2: Seller processes
order for three cases
read
read
Create Shipping
Event object
(E3)
Get relevant
Commissioning
event objects
(E1)
*redacted to include only SNs 123, 456, 789
Get relevant
Packing event
objects (E2)
E1*:
Commissioning
Events (case SNs
123, 456, 891)
send
E2: Packing Events
(case SNs 123,
456,891)
E3: Shipping Event
(case SNs 123,
456, 891)
Process incoming
Commissioning,
Packing, Shipping
Events
Verify scanned
physical goods
against Seller
events
S4: Three cases arrive
at buyer’s dock
SN 123, 456, 789
create
E3: Shipping
Event (case SNs
123, 456, 891)
O3
Create
Receiving Event
object (E4)
E4: Receiving
Event (case SNs
123, 456)
S5: Buyer receives SN
123, 456, but cannot
receive 789 because
there is no Shipping
event data
S6: Buyer quarantines
case SN 789 because
there is no shipping
event data
Situational: Cases are opened before put-away
Unpack cases
S7: Buyer notifies
seller of shipping event
discrepancy
E5: Unpacking
Event (case SNs
123, 456)
S8: Seller investigates
discrepancy between case 789
and 891, and determines the
previously recorded shipping
event is flawed. Seller voids the
previous Shipping event for SN
891 and creates a new Shipping
event for case SN 789.
Event
Object
Buyer
create
E1: Commissioning Events
E1i1
(LSU1)
Buyer Serialization Data Management
System
Network Exchange
Create Packing
Event objects
(E2)
create
S1
Business
Step
O1
O2
read
read
Process
incoming
Shipping Events
*redacted to include only SNs 789
Void Shipping
Event object
(E6)
Create
Shipping Event
object (E7)
create
create
E6:
Voidshipping
Event (case SN
891)
E7: Shipping
Event (case SN
789)
Get relevant
Commissioning
event objects
(E1)
Get relevant
Packing event
objects (E2)
send
E6:
Voidshipping
Event
(case SN 891)
E1*:
Commissioning
Events
(case SN 789)
E2: Packing
Event
(case SN 789)
E7: Shipping
Event
(case SN 789)
Verify scanned
physical goods
against Seller
events
Create
Receiving Event
object (E8)
E8: Receiving
Event (case SN
789)
Situational: Cases are opened before put-away
Unpack case
E9: Unpacking
Event (case SN
789)
S9: Buyer now receives
case SN 789
S1
System
Process
Step
Connector
Data Interface
Legend
Serialized Exception: Scenario 1-4B: Traceability data (incorrect Sold-To information in the Shipping event )
Seller Serialization Data Management
System
Seller
S0: Seller has serialized
Inventory On Hand
Create
Commissioning
Event objects
(E1)
trigger
S1
...
Buyer Serialization Data Management
System
E1in
(LSU n)
E2: Packing Events
E2[c-i]1
(case 1)
E2[c-i]2
(case 2)
...
E2[c-i]n
(case n)
LSU – Lowest Saleable Unit
E1c1
E1c2
E1cn
(case 1)
(case 2)
(case n)
S1: Buyer ABC places
order for three cases
...
S2: Seller processes
ABC’s order for three
cases
S3: Seller ships three physical
cases SN 123, 456, and 789.
While the physical products go to
ABC’s distribution center, the
Seller’s system records that the
Sold-To entity in the Shipping
Event is XYZ instead of ABC.
O2
O1
read
read
Create Shipping
Event object
(E3)
Get relevant
Commissioning
event objects
(E1)
*redacted to include only SNs 12, 456, 789
Get relevant
Packing event
objects (E2)
send
E1*:
Commissioning
Events (case SNs
123, 456, 789)
E2: Packing
Events (case SNs
123, 456,789)
E3: Shipping
Event (case SNs
123, 456, 789 with
Sold-To XYZ
Verify scanned
physical goods
against Seller
events
Process incoming
Commissioning,
Packing, Shipping
Events
S4: Three cases arrive
at buyer ABC’s dock
SN 123, 456, 789
create
E3: Shipping
Event (case SNs
123, 456, 789)
with Sold-To XYZ
S5: Buyer quarantines SN
123, 456, 789 due to
shipping event incorrectly
stating XYZ as the Sold-To
instead of ABC
O3
S6: Buyer notifies
seller of Sold-To
discrepancy in the
shipping event
S7: Seller investigates Sold-To
discrepancy, and determines the
previously recorded shipping
event is flawed. Seller voids the
previous Shipping event with XYZ
for SNs 123, 456, 789 and creates
a new Shipping event with ABC as
Sold-To .
Event
Object
Buyer
create
E1: Commissioning Events
E1i2
(LSU2)
Network Exchange
Create Packing
Event objects
(E2)
create
E1i1
(LSU1)
Business
Step
Create
voidShipping
Event object
(E4)
Create Shipping
Event object
(E5)
create
create
E4: voidShipping
Event (case SNs
123, 456, 789) with
XYZ as Sold-To
E5: Shipping
Event (case SNs
123, 456, 789) with
ABC as Sold-To
send
E4: voidShipping
Event
(case SNs 123, 456,
789) with Sold-To
XYZ
E5: Shipping Event
(case SNs 123, 456,
789) with Sold-To
ABC
Process incoming
Shipping Events
Verify scanned
physical goods
against Seller
events
Create
Receiving Event
object (E6)
E6: Receiving
Event (case SNs
123, 456, 789)
Situational: Cases are opened before put-away
Unpack cases
E7: Unpacking
Event (case SNs
123, 456, 789)
S8: Buyer now receives
case SN 123, 456, 789
S1
System
Process
Step
Connector
Data Interface
Legend
Serialized Exception: Scenario 1-5: Traceability Data is not received by buyer
Seller Serialization Data Management
System
Seller
S0: Seller has serialized
Inventory On Hand
Create
Commissioning
Event objects
(E1)
trigger
E1i2
(LSU2)
...
Buyer Serialization Data Management
System
E2: Packing Events
E1in
(LSU n)
E2[c-i]1
(case 1)
E2[c-i]2
(case 2)
...
E2[c-i]n
(case n)
LSU – Lowest Saleable Unit
E1c1
E1c2
E1cn
(case 1)
(case 2)
(case n)
S1: Buyer places order
for one case
...
S3: Seller ships one case.
Seller’s IT system records
the Shipping event for SN
123 but fails to transmit
corresponding EPCIS data
to buyer.
O2
O1
S2: Seller processes
order for one case
read
read
Create Shipping
Event object
(E3)
Get relevant
Commissioning
event objects
(E1)
Get relevant
Packing event
objects (E2)
create
E3: Shipping
Event (case SN
123)
O3
S4: One case arrives at
buyer’s dock
SN 123
S5: Buyer quarantines
case SN 123 because
there is no traceability
data to match the
physical product.
S6: Buyer notifies
seller of missing
traceability data
S7: Seller investigates missing
traceability data and
determines a transmission error
occurred. Seller IT system
triggers re-transmission of
event data for SN 123.
O3
O1
O2
read
read
read
*redacted to include only SN 123
Get Shipping
Event object
(E3)
Event
Object
Buyer
create
E1: Commissioning Events
E1i1
(LSU1)
Network Exchange
Create Packing
Event objects
(E2)
create
S1
Business
Step
Get relevant
Commissioning
event objects
(E1)
Get relevant
Packing event
objects (E2)
send
E1*:
Commissioning
Events
(case SN 123)
E2: Packing
Event
(case SN 123)
E3: Shipping
Event
(case SN 123)
Process incoming
Commissioning,
Packing, Shipping
Events
Verify scanned
physical goods
against Seller
events
Note: Read from previously created events
Create
Receiving Event
object (E4)
E4: Receiving
Event (case SN
123)
Situational: Cases are opened before put-away
Unpack case
E5: Unpacking
Event (case SN
123)
S8: Buyer now receives
case SN 123
S1
System
Process
Step
Connector
Data Interface
Legend
Business
Step
Serialized Exception: Scenario 2-1A: Shortage Discovered at Receiving (Fulfill missing case)
Seller Serialization Data Management
System
Seller
S0: Seller has serialized
Inventory On Hand
Create
Commissioning
Event objects
(E1)
trigger
S1
...
E2: Packing Events
E1in
(LSU n)
E2[c-i]1
(case 1)
E2[c-i]2
(case 2)
...
E2[c-i]n
(case n)
LSU – Lowest Saleable Unit
E1c1
E1c2
E1cn
(case 1)
(case 2)
(case n)
S1: Buyer places order
for three cases
...
S2: Seller processes
order for three cases
S3: Seller ships two
physical cases by
mistake. IT systems
think 3 cases have
been shipped.
O2
O1
read
read
Create Shipping
Event object
(E3)
Buyer
create
E1: Commissioning Events
E1i2
(LSU2)
Get relevant
Commissioning
event objects
(E1)
*redacted to include only SNs 123, 456, 789
Get relevant
Packing event
objects (E2)
send
E1*:
Commissioning
Events (case SNs
123, 456, 789)
E2: Packing
Events (case SNs
123, 456, 789)
E3: Shipping
Event (case SNs
123, 456, 789)
Verify scanned
physical goods
against Seller
events
Process incoming
Commissioning,
Packing, Shipping
Events
S4: Two cases arrive at
buyer’s dock
SN 123, 456
create
E3: Shipping
Event (case SNs
123, 456, 789)
Create
Receiving Event
object (E4)
O3
S5: Buyer receives SN
123, 456, but cannot
receive 789 because
physical case is missing
E4: Receiving
Event (case SNs
123, 456)
Situational: Cases are opened before put-away
Unpack cases
S6: Buyer notifies
seller of missing case
SN 789
E5: Unpacking
Event (case SNs
123, 456)
S7: Seller investigates
shipping discrepancy. Since
case SN 789 was omitted
from the shipment, seller
voids the prior shipping
event for SN 789.
Create
voidShipping
Event object
(E6)
create
S8: Seller processes 2nd
shipment to fulfill 3rd case in
the order.
Event
Object
Create Packing
Event objects
(E2)
create
E1i1
(LSU1)
Network Exchange
Buyer Serialization Data Management
System
E6:
voidShipping
Event (case SN
789)
send
E6: voidShipping
Event (case SN
789)
Process incoming
voidShipping Event
S1
System
Process
Step
Connector
Data Interface
Legend
Serialized Exception: Scenario 2-1B: Shortage Discovered at Receiving (Cancel)
Seller Serialization Data Management
System
Seller
S0: Seller has serialized
Inventory On Hand
Create
Commissioning
Event objects
(E1)
trigger
E1i2
(LSU2)
...
Buyer Serialization Data Management
System
E2: Packing Events
E1in
(LSU n)
E2[c-i]1
(case 1)
E2[c-i]2
(case 2)
...
E2[c-i]n
(case n)
LSU – Lowest Saleable Unit
E1c1
E1c2
E1cn
(case 1)
(case 2)
(case n)
S1: Buyer places order
for three cases
...
S2: Seller processes
order for three cases
S3: Seller ships two
physical cases by
mistake. IT systems
think 3 cases have
been shipped.
O2
O1
read
read
Create Shipping
Event object
(E3)
Get relevant
Commissioning
event objects
(E1)
*redacted to include only SNs 123, 456, 789
Get relevant
Packing event
objects (E2)
send
E1*:
Commissioning
Events (case SNs
123, 456, 789)
E2: Packing
Events (case SNs
123, 456, 789)
E3: Shipping
Event (case SNs
123, 456, 789)
Verify scanned
physical goods
against Seller
events
Process incoming
Commissioning,
Packing, Shipping
Events
S4: Two cases arrive at
buyer’s dock
SN 123, 456
create
E3: Shipping
Event (case SNs
123, 456, 789)
Create
Receiving Event
object (E4)
O3
S5: Buyer receives SN
123, 456, but cannot
receive 789 because
physical case is missing
E4: Receiving
Event (case SNs
123, 456)
Situational: Cases are opened before put-away
Unpack cases
E5: Unpacking
Event (case SNs
123, 456)
S7: Seller investigates
shipping discrepancy. Since
case SN 789 was omitted
from the shipment, seller
voids the prior shipping
event for SN 789.
Event
Object
Buyer
create
E1: Commissioning Events
E1i1
(LSU1)
Network Exchange
Create Packing
Event objects
(E2)
create
S1
Business
Step
Create
voidShipping
Event object
(E6)
create
E6:
voidShipping
Event (case SN
789)
send
E6: voidShipping
Event (case SN
789)
Process incoming
voidShipping Event
S6: Buyer notifies seller
of missing case SN 789.
Buyer also cancels the
remaining order for the
missing case.
S1
System
Process
Step
Connector
Data Interface
Legend
Serialized Exception: Scenario 2-2: Quantity Inference (Concealed Shortage)
Seller Serialization Data Management
System
Seller
S0: Seller has serialized
Inventory On Hand
Create
Commissioning
Event objects
(E1)
trigger
E1i2
(LSU2)
...
Buyer Serialization Data Management
System
E2: Packing Events
E1in
(LSU n)
E2[c-i]1
(case 1)
E2[c-i]2
(case 2)
...
E2[c-i]n
(case n)
LSU – Lowest Saleable Unit
E1c1
E1c2
E1cn
(case 1)
(case 2)
(case n)
S1: Buyer places order
for one case
...
S2: Seller processes
order for one case
S3: Seller physically
ships one case thinking
there are twelve
serialized lowest
saleable units in the
case.
O2
O1
read
read
Create Shipping
Event object
(E3)
Get relevant
Commissioning
event objects
(E1)
*redacted to include only SNs 123
Get relevant
Packing event
objects (E2)
send
E1*:
Commissioning
Events (case
SNs 123)
E2: Packing
Events (case SN
123)
E3: Shipping
Event (case SN
123)
Verify scanned
physical goods
against Seller
events
Process incoming
Commissioning,
Packing, Shipping
Events
S4: One case arrives at
buyer’s dock
SN 123
create
E3: Shipping
Event (case SN
123)
Create
Receiving Event
object (E4)
E4: Receiving
Event (case SN
123)
Unpack case
Verify scanned
physical goods
against Seller
events
E5: Unpacking
Event (case SN
123)
S8: Seller investigates SN 111,
the missing serialized lowest
saleable unit, which should have
been packed inside case SN 123
and shipped to the buyer. The
seller voids the previous shipping
event for SN 111.
Event
Object
Buyer
create
E1: Commissioning Events
E1i1
(LSU1)
Network Exchange
Create Packing
Event objects
(E2)
create
S1
Business
Step
Create
voidShipping
Event object
(E6)
create
E6: voidShipping
Event (lowest
saleable unit SN
111)
send
E6: voidShipping
Event (lowest
saleable unit SN
111)
Process incoming
voidShipping Event
S5: Buyer receives SN
123
S6: Buyer opens up case
SN 123 and discovers
there are only eleven SNs
inside. Case SN 123 is
missing a lowest saleable
unit SN 111.
S7: Buyer notifies
seller about shortage
of lowest saleable unit,
SN 111, missing from
case SN 123.
S1
System
Process
Step
Connector
Data Interface
Legend
Serialized Exception: Scenario 2-3: Undelivered or Lost shipment (Traceability data transmitted without physical product arriving)
Seller Serialization Data Management
System
Seller
S0: Seller has serialized
Inventory On Hand
Create
Commissioning
Event objects
(E1)
trigger
S1
...
E2: Packing Events
E1in
(LSU n)
E2[c-i]1
(case 1)
E2[c-i]2
(case 2)
...
E2[c-i]n
(case n)
LSU – Lowest Saleable Unit
E1c1
E1c2
E1cn
(case 1)
(case 2)
(case n)
S1: Buyer places order
for one case
...
S2: Seller processes
order for one case
S3: Seller ships one
physical case, SN 123.
Seller’s IT system records
the Shipping event for SN
123.
O2
O1
read
read
Create Shipping
Event object
(E3)
Get relevant
Commissioning
event objects
(E1)
*redacted to include only SNs 123
Get relevant
Packing event
objects (E2)
send
E1*:
Commissioning
Events (case SN
123)
E2: Packing
Events (case SN
123)
E3: Shipping
Event (case SN
123)
Process incoming
Commissioning,
Packing, Shipping
Events
S4: Buyer receives an
invoice for the previously
placed order but the
physical shipment of case
SN 123 never arrived at
the Buyer’s DC.
create
E3: Shipping
Event (case SN
123)
S5: Buyer investigates
missing case SN 123 for
which buyer has
supporting event data but
missing physical product.
O3
S6: Buyer notifies
seller of missing
shipment.
S7: Upon investigating the
reported missing shipment,
the seller determines that a
delivery problem occurred.
Seller voids the previously
recorded shipping event for
SN 123.
Event
Object
Buyer
create
E1: Commissioning Events
E1i2
(LSU2)
Buyer Serialization Data Management
System
Create Packing
Event objects
(E2)
create
E1i1
(LSU1)
Network Exchange
Business
Step
Create
voidShipping
Event object
(E4)
create
E4: voidShipping
Event (case SN
123)
send
E4: voidShipping
Event (case SN
123)
Process incoming
voidShipping Event
S1
System
Process
Step
Connector
Data Interface
Legend
Serialized Exception: Scenario 3-1A: Damaged Shipment (Return product to seller)
Seller
S0: Seller has serialized
Inventory On Hand
Function
Business
Step
Seller Serialization Data Management
System
Create
Commissioning
Event objects
(E1)
trigger
S1
...
E1in
(LSU n)
E2: Packing Events
E2[c-i]1
(case 1)
E2[c-i]2
(case 2)
...
E2[c-i]n
(case n)
LSU – Lowest Saleable Unit
E1c1
E1c2
E1cn
(case 1)
(case 2)
(case n)
S1: Buyer places order
for one case
...
S2: Seller processes
order for one case
S3: Seller ships one
physical case, SN 123.
Seller’s IT system
records the Shipping
event for SN 123.
O2
O1
read
Create Shipping
Event object
(E3)
Get relevant
Commissioning
event objects
(E1)
read
Get relevant
Packing event
objects (E2)
*redacted to include only SNs 123
send
E1*:
Commissioning
Events (case
SNs 123)
E2: Packing
Events (case SNs
123)
E3: Shipping
Event (case SNs
123)
Process incoming
Commissioning,
Packing, Shipping
Events
Verify scanned
physical goods
against Seller
events
S4: One case arrives at
buyer’s dock
SN 123
create
E3: Shipping
Event (case SN
123)
Create
Receiving Event
object (E4)
E4: Receiving
Event (case SN
123) disposition
= damaged
S5: Buyer detects that
physical case SN 123
arrives damaged. Buyer
receives SN 123 with a
disposition of damaged.
S6: Buyer quarantines
damaged case 123.
S7: Buyer notifies
seller that damaged
case SN 123 is being
returned.
S8: Seller receives
back damaged case
SN 123.
Event
Object
Buyer
create
E1: Commissioning Events
E1i2
(LSU2)
Buyer Serialization Data Management
System
Create Packing
Event objects
(E2)
create
E1i1
(LSU1)
Network Exchange
S1
System
Process
Step
Connector
Data Interface
Legend
Serialized Exception: Scenario 3-1B: Damaged Shipment (Rare case: Product is Destroyed by Buyer)
Seller Serialization Data Management
System
Seller
S0: Seller has serialized
Inventory On Hand
Create
Commissioning
Event objects
(E1)
trigger
S1
...
Buyer Serialization Data Management
System
E1in
(LSU n)
E2: Packing Events
E2[c-i]1
(case 1)
E2[c-i]2
(case 2)
...
E2[c-i]n
(case n)
LSU – Lowest Saleable Unit
E1c1
E1c2
E1cn
(case 1)
(case 2)
(case n)
S1: Buyer places order
for one case
...
S2: Seller processes
order for one case
S3: Seller ships one
physical case, SN 123.
Seller’s IT system
records the Shipping
event for SN 123.
O2
O1
read
Create Shipping
Event object
(E3)
Event
Object
Buyer
create
E1: Commissioning Events
E1i2
(LSU2)
Network Exchange
Create Packing
Event objects
(E2)
create
E1i1
(LSU1)
Business
Step
Get relevant
Commissioning
event objects
(E1)
read
*redacted to include only SNs 123
Get relevant
Packing event
objects (E2)
send
E1*:
Commissioning
Events (case
SNs 123)
E2: Packing
Events (case SNs
123)
E3: Shipping
Event (case SNs
123)
Process incoming
Commissioning,
Packing, Shipping
Events
Verify scanned
physical goods
against Seller
events
S4: One case arrives at
buyer’s dock
SN 123
create
E3: Shipping
Event (case SN
123)
Create
Receiving Event
object (E4)
E4: Receiving
Event (case SN
123) disposition
= damaged
S5: Buyer detects that
physical case SN 123
arrives damaged. Buyer
receives SN 123 with a
disposition of damaged.
S6: Buyer quarantines
damaged case 123.
S7: Buyer notifies
seller that case SN 123
is damaged.
S8: Seller authorizes
the destruction of
damaged case SN
123.
S9: Buyer sends
damaged case SN 123
for destruction.
Create
Destroying
Event object
(E5)
E5: Destroying
Event (case SN
123)
S1
System
Process
Step
Connector
Data Interface
Legend
Serialized Exception: Scenario 4-1: Product Inference Problem
Seller Serialization Data Management
System
Seller
S0: Seller has serialized
Inventory On Hand
Business
Step
Create
Commissioning
Event objects
(E1)
trigger
S1
...
E1in
(LSU n)
E2: Packing Events
E2[c-i]1
(case 1)
E2[c-i]2
(case 2)
...
E2[c-i]n
(case n)
LSU – Lowest Saleable Unit
E1c1
E1c2
E1cn
(case 1)
(case 2)
(case n)
S1: Buyer places order
for one case
...
S2: Seller processes
order for one case
S3: Seller physically
ships one case thinking
there are twelve
serialized lowest
saleable units in the
case.
read
Get relevant
Commissioning
event objects
(E1)
read
*redacted to include only SNs 123
Get relevant
Packing event
objects (E2)
send
create
E1*:
Commissioning
Events (case SNs
123, LSU SNs 100111)
E2: Packing Events
(LSU SNs 100-111
into case SN 123)
E3: Shipping Event
(case SN 123)
Verify scanned
physical goods
against Seller
events
Process incoming
Commissioning,
Packing, Shipping
Events
E3: Shipping
Event (case SN
123)
Create
Receiving Event
object (E4)
E4: Receiving
Event (case SN
123)
Unpack case
E5: Unpacking
Event (case SN
123)
Verify scanned
physical goods
against Seller
events
S4: One case arrives at
buyer’s dock
SN 123
S5: Buyer receives SN
123
S6: Buyer opens up case SN 123
and discovers there are twelve
SNs inside. Buyer detects two
problems in the shipment:
there’s an extra lowest saleable
unit SN 113 and a missing
lowest saleable unit SN 111.
S7: Buyer quarantines
extra lowest saleable
unit SN 113 because
there is no data.
S8: Buyer notifies seller of
the missing lowest saleable
unit SN 111 and informs
seller that buyer is
returning extra lowest
saleable unit SN 113.
S9: Seller investigates the dual
issue of missing SN 111 and
extra SN 113. The seller
rectifies the missing lowest
saleable unit, SN 111, by
voiding the previously
recorded shipment.
Create
voidShipping
Event object
(E6)
create
S10: Seller receives
back the extra lowest
saleable unit, SN 113.
S1
O2
O1
Create Shipping
Event object
(E3)
Event
Object
Buyer
create
E1: Commissioning Events
E1i2
(LSU2)
Buyer Serialization Data Management
System
Create Packing
Event objects
(E2)
create
E1i1
(LSU1)
Network Exchange
E6: voidShipping
Event (lowest
saleable unit SN
111)
send
E6:: voidShipping
Event (lowest
saleable unit SN
111)
Process incoming
voidShipping Event
System
Process
Step
Connector
Data Interface
Legend
Serialized Exception: Scenario 4-2A: Shipment for Buyer “Y”, arrives at Buyer “X” (Buyer X is not a customer of Seller, Buyer refuses to receive product from carrier )
Seller Serialization Data Management
System
Seller
S0: Seller has serialized
Inventory On Hand
Create
Commissioning
Event objects
(E1)
trigger
S1
S3: Seller mistakenly ships one case
to Buyer X’s DC. Physical shipment
has SN 123. While the physical
products go to Buyer X’s DC, the
Seller’s system records that the
Sold-To and Ship-To entities in the
Shipping Event are respectively, Y
and Y’s DC.
Buyer X
...
E1in
(LSU n)
E2: Packing Events
E2[c-i]1
(case 1)
E2[c-i]2
(case 2)
...
E2[c-i]n
(case n)
LSU – Lowest Saleable Unit
E1c1
E1c2
E1cn
(case 1)
(case 2)
(case n)
S1: Buyer Y places
order for one case
...
S2: Seller processes
Buyer Y’s order for one
case
Buyer X Serialization
Data Management System
Buyer Y
create
E1: Commissioning Events
E1i2
(LSU2)
Buyer Y Serialization
Data Management System
Create Packing
Event objects
(E2)
create
E1i1
(LSU1)
Network Exchange
Business
Step
S1
O2
O1
read
Get relevant
Commissioning
event objects
(E1)
Create Shipping
Event object
(E3)
read
*redacted to include only SNs 123
Get relevant
Packing event
objects (E2)
send
E1*:
Commissioning
Events (case SNs
123)
E2: Packing
Events (case SN
123)
E3: Shipping
Event (case SN 123)
with Sold-To as Y
and Ship-To as Y’s
DC
Process incoming
Commissioning,
Packing, Shipping
Events
create
E3: Shipping Event
(case SNs 123) with
Sold-To as Y and
Ship-To as Y’s DC
O3
S4: One case, SN 123,
arrives at buyer X’s
dock
SN 123
S5: Buyer X refuses to
receive case SN 123
from carrier.
S6: Upon investigating the
discrepancy in the shipping event,
the seller determines SN 123 is
legitimate but the shipment intended
for Buyer Y was incorrectly delivered
to Buyer X. The Seller voids the
previously recorded Shipping event
with incorrect Sold-To and Ship-To
values.
Create
voidShipping
Event object
(E4)
create
E4: voidShipping
Event (case 123) with
Sold-To as Y and
Ship-To as Y’s DC
send
E4: voidShipping Event
(case SN 123) with SoldTo as Y and Ship-To as
Y’s DC
Process incoming
voidShipping Event
Event
Object
System
Process
Step
Connector
Data Interface
Legend
Serialized Exception: Scenario 4-2B: Shipment for Buyer “Y”, arrives at Buyer “X” (Buyer Y refutes invoice, Seller voids shipment)
Seller Serialization Data Management
System
Seller
S0: Seller has serialized
Inventory On Hand
Create
Commissioning
Event objects
(E1)
trigger
S1
...
E1in
(LSU n)
E2: Packing Events
E2[c-i]1
(case 1)
E2[c-i]2
(case 2)
...
E2[c-i]n
(case n)
LSU – Lowest Saleable Unit
E1c1
E1c2
E1cn
(case 1)
(case 2)
(case n)
S1: Buyer Y places
order for one case
...
S2: Seller processes
Buyer Y’s order for one
case
S3: Seller mistakenly ships one case
to Buyer X’s DC. Physical shipment
has SN 123. While the physical
products go to Buyer X’s DC, the
Seller’s system records that the
Sold-To and Ship-To entities in the
Shipping Event are respectively, Y
and Y’s DC.
O2
O1
read
Create Shipping
Event object
(E3)
Get relevant
Commissioning
event objects
(E1)
read
*redacted to include only SNs 123
Get relevant
Packing event
objects (E2)
send
E1*:
Commissioning
Events (case SNs
123)
E2: Packing
Events (case SN
123)
E3: Shipping
Event (case SN 123)
with Sold-To as Y
and Ship-To as Y’s
DC
Process incoming
Commissioning,
Packing, Shipping
Events
create
S4: Invoice for case SN
123 is received by
Buyer Y.
E3: Shipping Event
(case SNs 123) with
Sold-To as Y and
Ship-To as Y’s DC
O3
S5: Buyer Y
investigates missing
case SN 123.
S6: Buyer Y refutes
invoice and notifies
seller of missing
shipment.
S7: Upon investigating the
discrepancy in the shipping
event, the seller determines
Buyer Y’s order was processed
incorrectly and shipment
intended for Buyer Y was
incorrectly delivered to Buyer X.
S8: Seller voids the previous
Shipping event with incorrect
Sold-To and Ship-To values.
Event
Object
Buyer Y
create
E1: Commissioning Events
E1i2
(LSU2)
Buyer Y Serialization
Data Management System
Create Packing
Event objects
(E2)
create
E1i1
(LSU1)
Network Exchange
Business
Step
Create
voidShipping
Event object
(E4)
create
E4: voidShipping
Event (case 123) with
Sold-To as Y and
Ship-To as Y’s DC
send
E4: voidShipping Event
(case SN 123) with SoldTo as Y and Ship-To as
Y’s DC
Process incoming
voidShipping Event
S1
System
Process
Step
Connector
Data Interface
Legend
Serialized Exception: Scenario 4-2C: Shipment for Buyer “Y”, arrives at Buyer “X” (Buyer X is a customer of Seller, Buyer keeps product)
Seller Serialization Data Management
System
Seller
S0: Seller has serialized
Inventory On Hand
Create
Commissioning
Event objects
(E1)
trigger
S1
S3: Seller mistakenly ships one
case to Buyer X’s DC. While the
physical products go to Buyer X’s
DC, the Seller’s system records
that the Sold-To and Ship-To
entities in the Shipping Event are
respectively, Y and Y’s DC.
Buyer X
...
E1in
(LSU n)
E2: Packing Events
E2[c-i]1
(case 1)
E2[c-i]2
(case 2)
...
E2[c-i]n
(case n)
LSU – Lowest Saleable Unit
E1c1
E1c2
E1cn
(case 1)
(case 2)
(case n)
S1: Buyer Y places
order for one case
...
S2: Seller processes
Buyer Y’s order for one
case
Buyer X Serialization
Data Management System
Buyer Y
create
E1: Commissioning Events
E1i2
(LSU2)
Buyer Y Serialization
Data Management System
Create Packing
Event objects
(E2)
create
E1i1
(LSU1)
Network Exchange
Business
Step
S1
O2
O1
read
read
Get relevant
Commissioning
event objects
(E1)
Create Shipping
Event object
(E3)
*redacted to include only SNs 123
Get relevant
Packing event
objects (E2)
send
E1*:
Commissioning
Events (case SNs
123)
E2: Packing
Events (case SN
123)
E3: Shipping
Event (case SN 123)
with Sold-To as Y
and Ship-To as Y’s
DC
Process incoming
Commissioning,
Packing, Shipping
Events
create
E3: Shipping Event
(case SNs 123) with
Sold-To as Y and
Ship-To as Y’s DC
O3
S4: One case arrives at
buyer X’s dock
SN 123
S5: Buyer X
quarantines case SN
123 because there’s no
traceability data
S6: Buyer X conveys
that it wants to keep
the product
S7: Upon investigating the
discrepancy in the shipping event,
the seller determines SN 123 is
legitimate but the shipment intended
for Buyer Y was incorrectly delivered
to Buyer X. The Seller voids the
previously recorded Shipping event
with incorrect Sold-To and Ship-To
values.
Create
voidShipping
Event object
(E4)
E4: voidShipping Event
(case SN 123) with SoldTo as Y and Ship-To as
Y’s DC
send
Process incoming
voidShipping Event
create
E4: voidShipping
Event (case 123) with
Sold-To as Y and
Ship-To as Y’s DC
O1
S8: Seller enters an order
for Buyer X and creates a
shipping event with Buyer X
as Sold-To and Ship-To
reflecting the prior physical
shipment.
O2
read
read
Create Shipping
Event object
(E5)
Get relevant
Commissioning
event objects
(E1)
Get relevant
Packing event
objects (E2)
*redacted to include only SN 123
send
E1*: Commissioning
Events
(case SN 123)
E2: Packing Event
(case SN 123)
E5: Shipping Event
(case SN 123) with
Sold-To as X and ShipTo as X’s DC
Process incoming
Commissioning,
Packing, Shipping
Events
Verify scanned
physical goods
against Seller
events
Note: Read from previously created events
create
E5: Shipping Event
(case SN 123) with
Sold-To as X and
Ship-To as X’s DC
Create
Receiving Event
object (E6)
E6: Receiving
Event (case SN
123)
Situational: Cases are opened before put-away
Unpack case
E7: Unpacking
Event (case SN
123)
S9: Buyer X now
receives case SN 123
Event
Object
System
Process
Step
Connector
Data Interface