Hello! We are setting up a Shopify POS app with a hybrid fulfillment model: customers can do cash-and-carry on site as well as purchase items for backend fulfillment in NetSuite. The storefront is working well but the items that were already “picked-up” are showing up as line items in the NetSuite sales order and we want them filtered out. We’re attempting to use the “Items : Create Line” mapping to define which items should be filtered from the sales order so they aren’t double-fulfilled. However, no matter what we set this value to the line items are still being pushed into NetSuite. We do have a valid line item field we can use to set this to true or false, but it’s not working as advertised. I have also hard-coded this mapping to “false” with no affect (see below).
I know that these mappings can be affected by position so in our mapping for items I have “Items : Replace All Lines” defined first, “Items : Create Line” defined next, and then all other line item mappings after.
Example: I have literally set the value of this field to “false” to see if it’s even being picked up.
I would have expected this sales order create to fail because there would be no line items. However, the SO was created with all lines (it’s sandbox data so take it for what it is).
@basvanditzhuijzen Thank you for the response. I wish I could map a proper boolean, but I don’t seem to be able to. Even if I set the field type to Boolean it still maps as a string
“celigo_createline”: “false”
I’ll try the “T”/”F” method, forgot about that. Thanks again!
I would like to try this out on my end. Are you using a Shopify-NetSuite integration app or a custom flow to sync your orders?
Also, since you’ve created the order on Shopify, is the Item present on the Shopify order? If yes, wouldn’t this affect how your accounting balances work since it does not match what’s on Shopify?
Strange, I just tested this and both “T“/”F” and boolean true/false (coming directly from the source, the NS mapper can’t create it as you found out.) and it worked ok.
This was a custom flow though, might be that there are some pre/postsubmit scripts in the IA messing with it.
@ellyxzerdavidjohn12, we’re using the Shopify-NetSuite integration app. I probably could have created a case to address this but I typically always work with custom flows so I posted here out of habit.
Re: the NetSuite line items and accounting: yes, the lines are in the Shopify order. We are testing a hybrid fulfillment model using two separate locations in Shopify: one for on–site purchase and one for backend fulfillment. Customers can purchase product directly at our trade show but also purchase product for shipment in a single order. We wanted only the unfulfilled items to be pushed to NetSuite. We’ve never done this before and we were still testing this so whether or not this approach would have worked is still unknown, but we weren’t able to get the lines removed so it’s moot.
FWIW, we ended up passing the fulfilled line items as closed in NetSuite so fulfillment would only fulfill those that weren’t. It’s a bit of workaround and there’s some accounting magic needed when creating the cash sale, but it works for us given our show starts today. However, I would still like to understand why removing the lines wouldn’t work for us.
Since you are using a Shopify integration app, your configuration options are limited to how the app is designed to function. The integration app (IA) operates on a one-to-one process flow and can only handle transactions within its predefined structure. If you attempt to configure it so that line items are removed from the original order, it creates a chain reaction that disrupts other dependent flows.
For example, if a customer later requests an exchange or refund for an item that was purchased and is removed on the NetSuite order, the IA will not be able to process that transaction properly since there is no longer a reference (etail order line id) to the original line item. This also causes downstream issues in accounting and inventory management, as items may appear as purchased without leaving a proper audit trail to track when or how many were included in the order.
In summary, the order record serves as the primary reference point for all other flows. If you proceed with removing line items from the original order, you would likely need to develop multiple custom flows to handle the downstream processes that are impacted.
@ellyxzerdavidjohn12 Thanks for the reply. I appreciate the feedback re: the implications of removing lines. Our team did not have a lot of time to react to this change in our process and we were exercising options. Understanding that this is not a recommended approach, what I really need to know is if the line removal feature is not available or functional for IAs? I don’t particularly like it when I enable or use features that are advertised to work and they don’t and there’s no reason as to why.
We’re moving forward with a hybrid purchase model for our trade shows, that is our reality. If it forces us to refactor our flow logic then so be it, we’ll deal with it if an when it happens. But I do appreciate the feedback.
This is not a feature available for our IA, as this is not recommended for any process. The IA makes sure that all information from the Shopify Order is synced to NetSuite, which also ensures that all information needed when transforming the order is present.
