|
We use Manhattan WM Software for Distribution. Basically we get a block of
Tracking numbers from Fedex downloaded, and stored on the iseries with in
the software, then we print the label right from the software with the
Fedex barcode and various other requirements. We send a file nightly to
Fedex with all the shipping information of cartons that went out that day.
I would call Fedex and ask if you could set up something similar. Also we
print the UCC-128 barcode that identifies what is in the box to our system
right on the same label. We still have to print two labels sometimes as
some large companies require their own label format, but if you are
shipping to individuals or small companies you only need the one label.
Not sure where you are located, we are in NJ, but here is our contact at
Fedex, maybe he can help you.
Yetish Yetish
Customer Technology Consultant
Fedex Services
yetish.yetish@xxxxxxxxx
On Thu, Aug 7, 2014 at 9:09 AM, Alan Campin <alan0307d@xxxxxxxxx> wrote:
I have written plenty of Fedex label software using TCP/IP and socketsbut
I have no idea whether Fedex still supports that interface. When I workedhave
with Fedex they had dozens of different interfaces and I imagine they
more now. I would bet they have an HTTP interface now but anything isi
possible. Seems the place you need to start is FedEx.
On Thu, Aug 7, 2014 at 7:00 AM, Steve Richter <stephenrichter@xxxxxxxxx>
wrote:
We are looking for ways to more efficiently create and print fedexshipping
labels. Are there web services or other software from fedex that I canuse?
Or 3rd party software that will do the specific functions I need it todo?
We currently use fedex ship manager with an ODBC connection to the IBM
torecord
semi automate the process.
I need a more granular way to interface with FEDEX. One step would
stepthe weight of the shipper carton and create a tracking number. Next
iswould print a single FEDEX label. The third would create the master
tracking number and close the shipment as far as FEDEX is concerned.
What the warehouse does is pack items into shipper cartons. Each item
located.picked from a picklist. Once the shipper is full it is closed and ashipper
label is printed. That shipper label has what we call an SSCC barcodeback
printed on it. That SSCC number is unique so it can always be tracked
to the order.
Once the order is completely picked all the shippers are taken to the
shipping station where the FedEx shipping manager workstation is
are 4We scan the SSCC barcode of one of the shipper cartons. Using the ODBCpopulated.
connection to the IBM i all of the ship manager entry fields are
It is at this point that the process starts to break down. If there
isshipper cartons the user enters that value in fedex ship manager,completes
the shipment and 4 fedex labels are printed. A master tracking number
trackingcreated along with 4 individual tracking numbers. Thru the ODBCthe
connection ship manager writes 4 records to a table on the i containing
master tracking number, the tracking number and the SSCC carton numberthat
was scanned to populate the FEDEX fields to begin with.file
The problem is those 4 tracking records written to my tracking number
all contain the same SSCC carton number. So I can link a fedex
twonumber to a warehouse purchase order. But I cannot link it to thespecific
items in the shipper of that tracking number. And secondly there are
FEDEXlabels on the shipper carton where all we really need is the single
listshipping label.list
thanks,
-Steve
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.