We are doing some work for a non-grocery retailer who is implementing
the inbound 832 directly with some select trading partners for item
setup and item maintenance (as opposed to using a third-party catalog service).
The retailer has said they want to use the 879 instead of the 832 for
inbound pricing updates, as they feel the 879 provides more
flexibility for communicating price changes.
It's early in the project so we are just now beginning our in-depth
research and analysis on this, but my initial thought was it would be
best to implement a single transaction set if possible (the 832), as
long as the 832 can meet the business need for inbound pricing updates.
I'm also seeing some information which leads me to believe the 879 is
to be used only in conjunction with the 888 Item Maintenance
transaction (grocery transactions?), so are the 879 and 832 never
used together?
If anyone has any information regarding how others, especially in the
retail industry, handle the transmission of price changes to update
the price information originally transmitted via 832, I would appreciate it.
Thanks in advance for your feedback!
Jayne
...
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:
mailto:[EMAIL PROTECTED]
mailto:[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/
