Hi all,

I'm new to the fulfilment side of things and am trying to find out if a suggested format from a warehouse is a standard way of doing things (to me Ubercart EDI's setup makes perfect sense, not theirs) - They are basically suggesting that instead of me exporting an order in the format of Delivery details and then numerous Order line numbers they want the Order line details followed by delivery information for EACH item on order by that person e.g.

Order product export pattern:

#, !qty, !model, !delivery_name, !delivery_street1, !delivery_street2, !delivery_city, !delivery_country_name, !delivery_postal_code, !user_comment

This doesn't actually seem possible to do with the Order product export pattern as it stands, is there a way I can do this without any major reworking of the module if they insist on this is how they want the .csv formatted?

Many thanks

Comments

jantoine’s picture

jantoine commented
Title: D6 - PRODUCT export patterns » Allow the use of order patterns in the product pattern field
Version: 5.x-1.x-dev » 6.x-1.x-dev
Category: support » feature

As to whether or not this is a standard practice for doing things, I do not know, but I do know I have seen this before.

This feature is on the roadmap. Updating the category to feature request and version to the 6.x-1.x branch.

Cheers,

Antoine

WebNewCastle’s picture

WebNewCastle commented

I actually need to do this same thing for someone. I have a fairly narrow time frame in which to complete it. But I'm going to see if I can work with this module and in a way that would allow for a contribution of a patch (or some code in that direction).

My guess is that ideally there would be an option presented in the settings to allow a choice between the two main approaches? Or is the plan / road map something different?

jantoine’s picture

jantoine commented
Status: Active » Closed (won't fix)

Hi WebNewCastle,

The future of this module is to eliminate the patterns altogether and replace them with template files that will allow anyone with basic php skills to create the exact export they need having access to all the data from the order, products, user, etc. I wrote a patch about a week ago that does exactly this... you can find it here: #957384: Use token hooks for replacement tokens and use template files instead of pattern variables.. Since that patch I have greatly changed head, so the patch most likely will no longer apply. I will most likely update the patch tonight as I need it for a meeting tomorrow morning.

The template file feature will not be integrated into the module until version 6.x-1.1, and right now we don't even have a 6.x-1.0 release. What I need help with right now is testing 6.x-1.0-alpha1 so we can move forward to the 6.x-1.1 release. A thorough review of 6.x-1.0-alpha1 would greatly help move things forward. In the meantime, you will be able to apply the updated patch giving you template file functionality.

Cheers,

Antoine

WebNewCastle’s picture

WebNewCastle commented

Ah ok. That sounds great. I should have picked up on that from the project page - moving a bit quickly right now. I need to get a particular integration done this week - and a particular manner - but, I can try find time to test out the alpha version later.