To add to what Craig said:

One of our clients is a supplier to military commissaries, in addition the 
retail resales market.

This supplier sells its product to military distributors who buy and warehouse 
the product and then sell it to the military at the same price they paid for it.

The transaction from the supplier to the military distributor is booked by the 
supplier as a regular sale.  When the military distributor sells the product to 
the military, the distributor sends the supplier an 867 reporting the sale to 
the military.

This 867 functions as a sales report against which sales commissions are paid 
by the supplier to the military distributor - a convoluted sales cycle to be 
sure, but its the industry standard and it works.

No where, however, is there any record of who buys the product from the 
military commissary,

Any EDI document can be used by any two trading partners for any purpose as 
long as it's a legal business transaction, but I agree with those who would 
expect the distributor to protect their end-user customer base like it was 
gold, if indeed they even knew who the real end-user was.

Good luck,

Dave Taylor
Sysmark Information Systems, Inc.
49 Aspen Way
Rolling Hills Estates, CA 90274
(O) 800-SYSMARK (800-797-6275)
(F) 310-377-3550
(C) 310-561-5200
www.sysmarkinfo.com
  ----- Original Message ----- 
  From: socal_ediguy 
  To: [email protected] 
  Sent: Sunday, October 09, 2011 2:50 PM
  Subject: [EDI-L] Re: End customer info


    
  > There are some retailers out their sending customer info for 
  > direct-to-consumer shipping of course -- 850 specs for DTC 
  > shipping; I don't have my specs handy, but IIRC there's also 
  > an EDI document for resales to end users -- I think it's an 
  > 867. I seem to remember a consumer/end user product 
  > warranty document as well.
  > 
  > The question of how one wants to use the information is 
  > going to be asked, but some distributor/retailers are more 
  > than happy to give up consumer data -- and even demanding 
  > their suppliers use it.

  Jim (and group)

  Yes, there is an 867 Product Transfer & Resale Report in the X12 spec. But I 
really don't think it's for the use suggested by our original poster. Here's 
what the spec says it's for:

  867 Product Transfer and Resale Report
  This Draft Standard for Trial Use contains the format and establishes the 
data contents of the Product Transfer and Resale Report Transaction Set (867) 
for use within the context of an Electronic Data Interchange (EDI) environment. 
The transaction set can be used to: (1) report information about product that 
has been transferred from one location to another; (2) report sales of product 
from one or more locations to an end customer; or (3) report sales of a product 
from one or more locations to an end customer, and demand beyond actual sales 
(lost orders). Report may be issued by either buyer or seller.

  Having posted that, I cannot see where the information being sent or received 
is about the end customer - beyond the fact that an item was sold to an end 
customer. There's is an N1 loop that could be used to send customer 
information, but, again, a lot depends upon the questions asked by nearly 
everybody that's replied - WHY is the company requesting this information?

  If it's possibly to follow the trail of a product that needs to be monitored 
(for possible recall later on - think food or medical), then it's maybe 
something valid. But it's still kind of questionable information....

  Most of the time, the data being sent by retailers to suppliers is more 
related to the sale of items and tracking goods for more of a "just in time" 
kind of ordering process, allowing the retailers and their suppliers to 
collaborate more on product levels.

  DTC...? I didn't find any DTC segment in the 850... At least in the 4010 
version of the spec. Are you referring to cross dock references - breaking up 
an order for a number of locations within a company...?

  Truly, the only reference to DTC I found in the spec is a DESTINATION CHARGE 
entry in the 150 "SPECIAL CHARGE OR ALLOWANCE CODE" element.

  Craig Dunham



  

[Non-text portions of this message have been removed]



------------------------------------

...
Please use the following Message Identifiers as your subject prefix: <SALES>, 
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work: <JOBS> IS 
REQUIRED in the subject line as a prefix.Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/EDI-L/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/EDI-L/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Reply via email to