FedEx Ship Manager
I have worked with FedEx Ship Manager before so I’m working to see if I can integrate Ship Manager with the Magento database.
I have installed Ship Manager and started identifying what I need to do to use the integrations in it to ship individual orders.
It appears that I need to create a view or something for the software to reference when pulling the order information.
I also need to figure out what to do to have it write back the tracking numbers back to Magento. It has the ability to insert records after it processes each package, and you can map which shipping field it inserts, but I need to figure out where I want them to go, and how I’m going to get it back into Magneto. Initially I’m thinking I might build a new table in the database to dump the shipping data to, and then (if I can figure it out/if it’s possible) write some kind of trigger to fire when a new record is inserted to update the magento records with the tracking numbers.
I’ve run into some issues with Ship Manager before where it doesn’t always write back tracking numbers, so I’m not sure how I’m going to address that yet.
1mjohnsonperl posted Tue, March 25, 2008
This may not be the best way to write a view in MySQL for Magento, but it’s at least a start.
http://www.magentocommerce.com/wiki/groups/207/fedex_-_shipping_view
...I now know that the comment space is limited here… so I have created a wiki document that contains the SQL for the view I created.
2mjohnsonperl posted Tue, March 25, 2008
This view was a bit of a mess to put together. It would seem there has to be a better way to do this, but I’m not real sure what it would be. The first query I put together I used a lot of joins, but that made the dumb thing about croack taking 10 times longer every time I added another table to join for one more attribute once I got up to 6 or 7. Here with the sub-select queries, it actually executes quickly on a database with 4 orders. I don’t know if it will have issues as the database grows though.
I probably need to have it filter the open orders or something like that so that as the database grows the view will only reference the smaller list of orders that haven’t shipped yet, instead of all orders from the beginning of time.