|
PRICE BRACKET v. 2.0.2 |
|
| Problem
Statement |
Price bracket communication is the process
of communicating the basic price bracket criteria between the seller, buyer and
any third party following communication of the core data elements of item and
party, as well as any subsequent maintenance messages. The price bracket
communication process reflects the required activity of a manufacturer or
supplier that wishes to provide a trade item for global trade. Price
communicates either a generic global price or the agreed upon negotiated price
between trading partners.
The Price Bracket provides the ability to
communicate the business rules associated with the criteria required to qualify
for varying levels of pricing for a trade item. It may accompany, precede or
follow the communication of a price.
This Price Bracket definition intentionally
does not support additional “business rules based” price communication, e.g.
temporary price reductions/promotions, variable measure pricing, efficiency
criteria associated with the trading partnership, allowances and charges, etc.
|
| Objective |
|
To supply the detail design of a Price
Bracket business transaction needed to meet the requirements of the referenced
BRAD(s).
|
| Audience |
|
The audience of
the standards would be any participant in the global supply chain. This would
include retailers, manufacturers, service providers and other third parties.
|
Business
Context
|
Industry:
All
Geopolitical: All
Product:
All
Process: Align
System
Capabilities:
EAN.UCC
Official
Constraints: None
|
|
Business
Transaction View
|
|
Price data alignment is the process of
communicating the Price data elements between the seller, buyer and any third
party.
|
| Business
Transaction Use Case
Diagram |
|
The diagram below illustrates the position
of the Price Bracket within the overall GS1 General Business Model
|
 |
Use Case
Description
|
| Use
Case Name: |
Add Price Bracket |
| Use
Case Description: |
There are two scenarios in the price
bracket communication process as described in problem statement of section 1.1.
Price bracket data alignment is considered part of the price data
communication. The price bracket data communication scenarios follow:
- Scenario 1 – Reference to one or more price brackets within the
Price communication.
- Scenario 2 – Price
Bracket definition sent independently (as a standalone document).
NOTE: An acknowledgement that there are
industry specific criteria that are used to define price brackets. These
attributes can be used across several business processes. (May be used within
scenario 1 or 2.)
The buyer and seller must make contact and
set up a business relationship before trade can proceed. This is a prerequisite
to all of the other steps. This initial contact can be made in many different
ways. Following the establishment of the trading agreement, the parties must
exchange their basic business data such as trading partner names, addresses,
locations, item attributes, price lists, contracts and trading partner agreements.
Specifically, the price data can be communicated as part of the Item alignment
data or in a subsequent separate message.
|
| Actors
(Goal): |
The primary actors
in the price bracket data alignment process are the "seller" and the
"buyer". Depending on the specific
nature of the relationship other actors may have a role. The seller identifies
price bracket data and sends the price data message(s). The data recipient
acknowledges the price data to complete the price data alignment activities. Ensuring the price data is aligned
facilitates other processes such as ordering, despatch advice and
invoicing.
- Seller, Manufacturer or supplier of the item.
- Buyer, Retailer or distributor of the item
- Third
Party, Other parties that somehow influence the item and may include creation,
distribution, publication, and/or maintenance of the item, serving as an agent
for a seller or a buyer.
|
| Performance
Goals: |
None |
| Preconditions:
|
The
price data alignment process begins when the following conditions have been
met.
- A trading relationship exists between buyer and seller
- Party information is aligned between buyer and seller
- Scenario 1 - Reference to one or more price brackets within the Price
communication. Item information has been
aligned between buyer and seller.
- Scenario
2 - Price Bracket definition sent
independently (as a standalone document).
The Item information does not have to be aligned between buyer and
seller because standalone price bracket definitions are not defined to specific
item(s).
|
| Postconditions: |
|
| Scenario: |
Begins when prices or price
bracket definitions have been agreed upon between the trading partners. This
process is to communicate the results of that agreement.
Continues
with...
|
Step
#
|
Actor
|
Activity
Step
|
|
1
|
Seller
|
Communicates
the price data.
|
|
2
|
Buyer
|
Receives
the price data.
|
|
3
|
Buyer
|
Acknowledges
the receipt of price data.
|
|
4
|
Seller
|
Receives
the price data acknowledgement to end the process
|
Ends
when the data recipient, upon receipt of
the price data communication, acknowledges as defined in the Global Data
Synchronization Business Requirement Document
|
|
Alternative
Scenario:
|
None |
Related
Requirements:
|
None |
Related
Rules:
|
None |
|
| Business
Transaction Activity Diagram |
 |
|
| Business
Transaction Sequence Diagram |
| No sequence Diagram |
|
| Implementation Considerations |
