What is the difference between a Minimum Order and a Community Order?
A 'minimum order' contains minimum data because it relies on the principle of referencing and defaults. Only mandatory information (i.e. supply reference, price, quantity) will be sent. Additional information is not allowed and will not be accepted by the Market Place. A minimum order must contain trade condition ‘301’ (Subject to agreed conditions), which emphasizes that the agreed trade conditions between supplier and customer apply (registrered by the Market Place or by written agreement).
Benefits of a minimum order:
- Time to market : Minimum implementation effort
- Fast : Less data to transmit
A market place which accepts ‘community orders’ validates all data specified in the order. If data is left out (e.g. package or delivery information) the Market Place will use customer defaults or referenced supply data.
Benefits of the community order:
- Flexibility: Allows the customer to choose between options offered (for package and delivery, specified in maximum supply)
- Unambiguous: Exactly specifying the product, price, selected options
What is the difference between a Minimum Supply and a Community Supply?
A 'minimum supply' contains minimum data. Only one package option, one delivery option (location) and no prices for packing/packages. It is not allowed to specify information above the minimum data. The customer will only validate the mandatory data. A minimum supply must contain trade condition ‘301’ (Subject to agreed conditions), which emphasizes that the agreed trade conditions between supplier and customer apply (registrered by the Market Place or by written agreement). Clock supply contains often minimum data.
Benefits of the minimum supply:
- Time to market: minimum implementation effort
- Fast: minimum data to transmit
A 'community supply' contains more than minimum data. Often it contains options for packing and delivery locations. But also additional information such as packing prices and so on. If data is left out (such as delivery price and/or package price), the customer will rely on defaults registrered by the Market Place.
Benefits of the 'community supply'
- Flexibility: Allows the customer to choose between options
- Details: more detailed supply information for the customer
I cannot find an example for the clock distribution packing list barcode (distribution)?
It can be specified within a ReferencedDocument component, the referenceID contains the barcode and the referencetype is 'BT'. For more details on the barcode itself see message guide CLOCKT "Invulinstructie_CLOCKT_3_7_Ex_KVV", worksheet 'Barcode opbouw" and an example in the message guide of the CC VMP Order.
Is it allowed to use different unit codes for the minimum and maximum quantity for the item price? for example minimum 1 bunch (coded 2) and maximum 100 boxes (coded 3).
No, for specifying quantum prices you must use multiple price options per unittype. For example:
Price 1.10 minimum 1 bunch, maximum 10 bunches.
Price 1.00 minimum 11 bunch, maximum 20 bunches.
Price 1.10 minimum 1 box, maximum 10 boxes.
Price 0.80 minimum 11 boxes, maximum 20 boxes.
Can I expect the distribution barcode in the order response?
Yes, but it depends on the market place to provide you this service. It is even possible that a customer provides the distribution barcode in the order instead of the supplier in its order response. But this is uncommon and should be regarded as an exception on the standard way of working. Therefore it is not to be expected that market places will accept barcodes provided by customers in their orders.
A supplier offers a product using a gross price. The additonal costs are specified within the packing and delivery components. Is it allowed to place an order using a net price including these costs?
No, the order is based on the supply data. If the supplier specifies a gross price, the order contains a gross price including the specified additional costs elements. In case of minimum supply data, additional costs may apply. This type of supply contains condition 301 'Subject to agreed condition' and therefore possible additional costs are listed within the defaults of the market place, and are not specified within the order.
Why must order information match on some details with the supply information?
The supplier must be sure that all conditions are understood and there expects that all conditions are returned in the order message. The customer could choose the receive minimum supply data and returning minimum order data. In this scenario condition code '301 Subject to agreed conditions' applies. Defaults of the market place will be applicable as agreed beforehand.
As a supplier, I do not want to specify a specific type of package for the product, how do I do this?
In an order the buyer must specify the package type the supplier has mentioned in his supply line. In case of different packaging options, the default option can be recognized by the scheme name of the package ID ("MB"). In case the supplier wants to decided which package type will be delivered, without using a specific package type code, he should use codelist ID "902", code '999' and schemeAngencyName "VBN". This is not yet formalised within the CC VMP community but accepted as a general instruction.
I want to offer a part of my supply to a specifc customer. I do not want other customers to read these offers. How can I be sure that a customets get's the offers especially made for him?
First, through basic authentication you can be sure the customer is your customer asking for supply information. Next to this, within your supply line you can specify the customer ID (CustomerParty) along with the document type '310' for selective offer. In the supply request line the customer may ask for only the selective supply lines by specifying document type '310' or without specifying a document type (he will receive 'general' supply lines including the ones especially made for him). Requesting supply based on document type is not one of the minimum request scenarios of the CC VMP Community. It depends on the market place if it will support an filter on the document type.
When a supply line contains price option with a minimum quantity unit 'bunch', is it then alllowed to order in boxes?
No, the unit type must be specified in the supply line within as price minimum order quantity unit. Rule 9.10: The order unit may be trolley, layer, box, bunch or stems. The unit type must be specified in the supply line as price minimum order quantity unit.