-
-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lock an Order #1081
Comments
Hey @czupet! I'm not aware of any method for locking an order except for fulfilling it and closing it. What kind of app are you building? Do you know why the customers change the shipping/billing addresses after they place the order? If you tell me a little about your usecase I might be able to help. |
We download an order, and our WMS (Warehouse Management System) loads the order into the database after the order is loaded into our WMS the inventory quantities are adjusted accordingly, and we cannot change the order that includes canceling the order.
Updating or cancelling must be done manually through WMS system's UI. That's why we want to prevent a customer from changing their order in Shopify including the address once the order is in WMS.
Amazon has 30 min window where you can change an order, I don't think Shopify has that function.
From: Joshua Harms ***@***.***>
Sent: Monday, July 8, 2024 4:38 PM
To: nozzlegear/ShopifySharp ***@***.***>
Cc: Peter Czurak ***@***.***>; Mention ***@***.***>
Subject: Re: [nozzlegear/ShopifySharp] Lock an Order (Issue #1081)
Hey @czupet<https://github.com/czupet>! I'm not aware of any method for locking an order except for fulfilling it and closing it. What kind of app are you building? Do you know why the customers change the shipping/billing addresses after they place the order?
If you tell me a little about your usecase I might be able to help.
-
Reply to this email directly, view it on GitHub<#1081 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABTZSUYJLYRJZ3K3MEHZRSLZLMBCNAVCNFSM6AAAAABKRTJ3N6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJVGM4TCMBTGE>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
Is your app built just for one shop, or is it something you're going to publish to the App Store/potentially use on multiple shops? If it's just for one shop, I think you could get away with editing your store's theme to just remove the order editing form so customers can't even use that. If that's not going to work, you may need to look into setting up your app as a Fulfillment Service. When you said you closed the orders and they didn't work, did you close them using fulfillment orders? Do you use those at all? |
It’s just one internal app, I used the close.json
API to close the order.
Peter Czurak
…________________________________
From: Joshua Harms ***@***.***>
Sent: Monday, July 8, 2024 5:02:29 PM
To: nozzlegear/ShopifySharp ***@***.***>
Cc: Peter Czurak ***@***.***>; Mention ***@***.***>
Subject: Re: [nozzlegear/ShopifySharp] Lock an Order (Issue #1081)
Is your app built just for one shop, or is it something you're going to publish to the App Store/potentially use on multiple shops? If it's just for one shop, I think you could get away with editing your store's theme to just remove the order editing form so customers can't even use that.
If that's not going to work, you may need to look into setting up your app as a Fulfillment Service. When you said you closed the orders and they didn't work, did you close them using fulfillment orders? Do you use those at all?
—
Reply to this email directly, view it on GitHub<#1081 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABTZSU5XVHRV7WG36TWZN2DZLMD7LAVCNFSM6AAAAABKRTJ3N6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJVGQZDGMJWGQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Is there any way to lock an order so a customer cannot change it?
I tried Closing an order and that works for the line items, but a customer can still change the Shipping and Billing addresses.
The text was updated successfully, but these errors were encountered: