Questions EDI Packing List Requirements
Hi all! I have a question to see if anyone has ever run across this situation. I have a client that currently does a lot of blind drop shipping for their EDI Trading Partners. For example, someone will buy on Home Depot's website, that order will come via EDI into Acumatica, and my customer ships it on behalf of Home Depot. The issue I am running into is that my client says that Home Depot is very strict on the formatting of the packing list. It should look as if Home Depot themselves sent the package. Home Depot does have specifications on where data needs to print and the template look with even specific pixel sizes and locations. The customer can print these packing slips out of their EDI system but they need to manually go in and put the information manually which basically negates any integration that they were looking to accomplish with Acumatica and their EDI provider. I am not 100% sure that the Acumatica Report Designer can handle the template requirements from their trading partners so I'm wondering if anyone has run into this before and what path did they take to resolve this. Back in my legacy days, we would use some overlay program where we can scan the template and then overlay the data over it. Any thoughts? I really appreciate any help you can provide.
We print custom, branded packslips for one of our customers - and yes, they are very strict on the formatting. These packslips are printed out of our WMS, not Acumatica, but the process could easily be adapted.
On their EDI purchase order they send all relevant consumer-facing data that needs to be displayed (merchandise total, tax, shipping cost, order total, the customers item description, etc.) These values are then parsed and stored in custom database tables when the order is brought into Acumatica. We have a separate packslip report file that meets their specifications. This includes their logo, report language, formatting, return policies which all dynamically changes either through formulas or subreports based on which of their branches the consumer purchased from. We do all of this in an older version of Crystal and I don't see any features that we're using that the Acumatica Report Designer can't use.
The biggest challenge will be how to store the EDI packslip values in Acumatica. This can be a headache depending on how variable the format is from various trading partners. Our data is fairly simple with one customer requiring this, so we got away with having one table with a row for each order and it has columns for each potential value they send. If you have an integration pulling down order data, you should be able to map these fields somewhere as well with minor customization.