Hi,
First of all thanks for such lovely module.
about the POS Return.. I think we should look for order number then the sku of individual products. as sometimes, we give 10% discount but if we forget to notice it from the money receipt, we might cash back the full amount....
as computer should do things automatically and without error.... I think this could be useful.
Steps:
1> click on Return menu of POS
2> enter the order number then load the items was in that order... OR, let user put a sku on their own
3> load the price should be returned..
4> complete the refund process
we can mange manually, but I think this should be the way... at least to avoid typo :)
Comment | File | Size | Author |
---|---|---|---|
#40 | pos-return-order-serach-2772927-40.patch | 321.91 KB | Hubbs |
#39 | pos-return-order-serach-2772927-39.patch | 318.3 KB | Hubbs |
#39 | pos-return-order-serach-2772927-39-screenshot.png | 151.52 KB | Hubbs |
#38 | pos-return-order-search-2772927-38.patch | 11.4 KB | Hubbs |
#37 | Screen Shot 2017-06-20 at 6.14.59 PM.png | 134.1 KB | shabana.navas |
Comments
Comment #2
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedI have taken an initial stab at the feature here: https://github.com/shabananavas/commerce_pos/tree/wip/pos-return-order-s.... Still left to do the pricing adjustment. The whole idea is that the item should be added with the actual price that the customer paid and not the default product price. But, unfortunately, I didn't get time to look into that yet and also need more input on how best to implement that.
Comment #3
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedA screenshot of how it would look.
Comment #4
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedPatch attached.
Comment #5
smccabe CreditAttribution: smccabe as a volunteer and at Acro Commerce commentedHey shabana,
The patch above is buggered, it looks like it got some merge conflict files in there as well? i see some .orig files. Can you reroll a clean version for review plz.
Comment #6
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedUpdated patch.
Comment #7
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedUpdated and clean patch against 7.x-2.x.
Comment #8
smccabe CreditAttribution: smccabe as a volunteer and at Acro Commerce commentedRerolled patch against -dev
Comment #9
smccabe CreditAttribution: smccabe as a volunteer and at Acro Commerce commentedComment #10
smccabe CreditAttribution: smccabe as a volunteer and at Acro Commerce commentedFixed up missing js file
Comment #11
smccabe CreditAttribution: smccabe as a volunteer and at Acro Commerce commentedhey @shabana.navas with the new modal stuff from travis being in head now, can you reroll this. I took a look at it but there are a lot of conflicts and probably easier for you to sort out than me.
Thanks!
Comment #12
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedLooks like part of the patch went in already in another commit. So, re-rolling the patch against the latest version with the pieces that were left out.
Comment #13
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedComment #14
Anonymous (not verified) CreditAttribution: Anonymous commentedI've reviewed the patch from #12 and it appears to work. I was a little confused at the validation function though, and ended up replacing it with a built-in element validate callback. See the interdiff patch attached.
I also noticed some odd styling issues (see screenshot) but I wasn't sure of the best way to fix them.
Functionally, the patch is great and I think can be merged without further changes, but I had a few thoughts as I was reviewing it:
1) The order that is referenced isn't altered in any way as a result of the return. This might be confusing for people... Would it be better to alter the order that is being returned so that any items returned from it are removed from the order, and apply a negative payment transaction to the order reflecting the amount that was refunded? That way, we could reconcile orders that were returned and numbers should match up.
2) The Commerce POS Receipt module uses the order id on the receipt but labels it as 'Order Number' (which isn't actually accurate, it is using the id). This might be confusing because the help text for this new Order return feature says to enter the order id, not the number. We should probably change the Commerce POS Receipt module so that it properly labels the order id as an order id, not number.
3) I'm not sure if this is happening, but are we incrementing stock for returned items? Should we be?
Comment #15
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedThanks @wildkatana for cleaning up the validation. I have attached a new patch with those changes incorporated. As for your suggestions, I think @smccabe or @tbradbury are best to answer that.
Comment #16
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedWoops forgot to attach patch.
Comment #17
travis-bradbury CreditAttribution: travis-bradbury at Acro Commerce commentedI think order number is the way to go. Isn't a commerce_order's order number always set to the order_id anyway when it's not modified by something? Can we use order number instead of having the note about using ID instead of number? I think it's asking a lot to have a cashier understand what the heck an order ID is versus an order number.
I attempted to kick off a review on the PR but I'm not sure it's the current state of the patch because it might not have been re-rolled against the latest dev.
Comment #18
Anonymous (not verified) CreditAttribution: Anonymous commentedI agree that Order Number is ideal for customer facing receipts and for cashiers as well. We should be consistent and use them in forms and elsewhere.
Comment #19
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedThanks guy, I'll make the changes you mentioned. I haven't updated the PR, will do that as soon as I make the recommended changes.
Comment #20
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedNew patch with changes recommended in #17 and #18 so that we're now searching by order number instead of ID.
I tried to update the PR but it had way too many conflicts and I kind of gave up :( and closed it out. Please use the patch to test this. Thanks.
Comment #21
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedComment #22
Anonymous (not verified) CreditAttribution: Anonymous commentedI didn't test it but I looked at the patch and can see that you made the changes I suggested. It would be nice to figure out the PR so we can review it more in-depth though... Have you tried making a new branch and applying your patch to it and making a new PR from that?
Comment #23
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedCreated new PR here: https://github.com/AcroMedia/commerce_pos/pull/43
Comment #24
smccabe CreditAttribution: smccabe as a volunteer and at Acro Commerce commentedComment #25
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedMore comment and code cleanup.
Comment #26
smccabe CreditAttribution: smccabe as a volunteer and at Acro Commerce commentedCode looks good, I'm gonna get jjpoole to go over it for bit of a UX review, for how to handle the 2 fields and the return button
Comment #27
smccabe CreditAttribution: smccabe as a volunteer and at Acro Commerce commentedjjpoole is doing a UX mock for this, he'll post when he's done.
Comment #28
jjpoole CreditAttribution: jjpoole commentedHere's a mockup. Toggle will focus the UX to one technique or the other, removing confusion around the two different ways to search.
Comment #29
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedThanks @jpoole for the mockup. Updated patch is attached.
Comment #30
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedFixed typo.
Comment #31
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedOops wrong patch.
Comment #32
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedComment #33
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedComment #34
jjpoole CreditAttribution: jjpoole commentedWe should either remove or update the "Start your return..." text, as it doesn't mention the ability to search for order ID.
Comment #35
smccabe CreditAttribution: smccabe as a volunteer and at Acro Commerce commentedFlipping back to needs work for the text change jjpoole mentioned.
Jason, did you also want to do any mockup for the modal that pops up for selecting the items from an order to return?
Comment #36
Anders PaulsenHey Shawn, I've added a mockup for that modal pop-up to the files below.
Comment #37
shabana.navas CreditAttribution: shabana.navas at Acro Commerce commentedThanks Anders. I have styled as best as I could (see attached image). Latest patch again 2.x-dev is attached.
Comment #38
Hubbs CreditAttribution: Hubbs at Acro Commerce commentedUpdated patch. Not much changed in this as all I did was remove the addition of a mac .DS_STORE file.
I'm going to clean up a bit of CSS next. stay tuned.
Comment #39
Hubbs CreditAttribution: Hubbs at Acro Commerce commentedUpdated styles in this patch to closer match the design mockups by @Anders Paulsen and @jjpoole. I ended up adding a very small amount of padding on the image top and bottom. The design has the images without this spacing and no top/bottom border, so, it looked odd if the content within the box was taller than what the design showed, like if the title wrapped. You would end up with space top and bottom of the image but no border. To further this, adding a top/bottom border doubled up the top and bottom border thickness when the image was right against it the item boundaries, which also looked odd. Adding this extra padding made this a non-issue and I don't think detracts from the overall design.
Here's a screenshot:
There are a few things I'd still like to do, but, I ran out of time today.
Comment #40
Hubbs CreditAttribution: Hubbs at Acro Commerce commentedUpdated patch that includes the remaining items I mentioned in #39.
Note: the modal close button was previously the
X
letter. I changed this incommerce_pos.common.inc
tot('Close')
for screen readers. The css hides the text and replaces it with an X image.Comment #42
smccabe CreditAttribution: smccabe as a volunteer and at Acro Commerce commented