https://netsuiteprofessionals.com logo
Join Slack
Powered by
Hi All, we have times where we will have an order ...
# general
a
Hi All, we have times where we will have an order that has products that will ship from two different warehouses. And they most likely will be fulfilled at different times. If line 1 is for warehouse A and they fulfill it then print the picking ticket, whenever the 2nd line that is getting fulfilled out of warehouse B the printing ticket is no longer in their to be printed que. Is there a way to work around this? Or a NetSuite feature that we can enable to handle this?
k
This was actually a large driver in a customization I worked on for a client to auto generate and send Pick tickets to the right printers.
They had some complex logic around which floor it printed to as opposed to different facilities.
However - there might be native function that accomplishes what you are looking for - which is to use fulfillment requests as opposed to fulfilling directly from the sales order
👍 1
It adds a transient step in the middle that allocates it to a warehouse for fulfillment - and so in your case your SO would wind up with 2 fulfillment requests, 1 for location A, and one for location B. And then they have their separate pick tickets I believe
I've never used it - so I'm talking hypotheticals here.
Key quote
Copy code
If multiple locations are specified at line-item level in a sales order, you must create at least one separate fulfillment request per location. For example, in a sales order with two line items, if the first line has a store location in Berkeley and the second line has a store location in San Mateo, you must create two fulfillment requests.
a
@KevinJ of Kansas Thank you, sir! I had thought about scripting something up, but I keep getting back to as soon as I mark that check box to be printed back to true, that warehouse A will see that ticket in their que again. From a fellow Kansas City NetSuite user.
k
The custom scripted solution was a bunch of line level fields, an XML -> PDF process and automated emails to a printer. It was painful, and if I could, I would avoid it in the future.
The fun part was figuring out how to avoid tripping NetSuite's spam filter.s
I would expect to have to code at least a little bit of logic on top of the transactions, but otherwise, the process should provide most of the bones you need as opposed to doing something from scratch.
z
I have used fulfillment requests in the past and I thought they worked really well. You can also create multiple item fulfillments against one fulfillment request which is really handy.
I've done the automated emails approach as well and usually add the tran id or the date to the subject line to avoid the spam filter
k
Oh, it's even pickier than that. Magic trick was unique email names with random strings at the end to make the titles "sufficiently different", plus DMARC and DKIM config, and making sure the script (back in the 1.0 days this wasn't the default) requested a read receipt.
Issue was triggered around 16 or 17 emails in a minute. Plus some threshold of number of emails in a day. NS couldn't tell me what threshold to stay under though, and that it was all "fuzzy logic"
4 Views
Open in Slack
PreviousNext
Powered by