Order Import Module Custom Filter Option
We would like the ability to create a custom filter for the Order Import Module. We'd like to catch orders when several criteria are met, not just the options you offer. If we could do this based on a SQL-like query, it would be super helpful.
Russ, I'm sorry I am responding so belatedly.
So the prime example would be to flag orders shipping to a specific address to catch orders shipping to an address known to be a problem. Currently we can only flag orders based off flags in the sender/customer account and/or order specific items.
This feature would also come in handy to flag orders that, for example, have a $0 balance, but do not contain a specific adcode. We will run a sale and purposefully have specific items come in with a $0 balance. but we need to make sure that OTHER orders/packages are not being affected. Hope that makes sense.
There are other instances this may come in handy, but those are the better examples I can think of right now.
The imported (and unverified) orders have not yet been stored in our tables so traditional SQL queries would not be possible. I understand you're asking for "SQL-like" queries but thought we should get that on the table first.
I'll provide one example that came up not too long ago. We had a request to have a validation check for orders whose customer had an outstanding balance, and another when that customer was set to 'do not accept orders'. Here these are not elements of the order data that could be queried but instead referenced their matching customer...which is not yet know (established during verify). Here special code had to be written to establish the customer match so that the customer data could be queried.
In summary, without being able to do typical SQL queries, we've instead had to program validation checks unique to their purpose. While this doesn't currently lend itself to an adhoc query, I don't want to discount it either.
We should examine some examples that are driving this request. If we find that having access to X, Y, and Z would fit most of the need, it would be worth exploring to see if/how we could make that happen.
To start the process I'd encourage you to post back here with some examples of cases you're trying to handle better, and what elements you'd want in the query. Consider if these examples are representative of most of the foreseeable need, as much as that can be known. Can we get it down to small set of criteria (e.g. X, Y, and Z) that, if you had them, would largely address the need.
I will close by stating that generally it is not too difficult for us to add new (specific) validation checks. While we do charge custom programming for them, they are typically only two hours. Each year we add more and expect the list to continue to grow.