Skip to content
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

Tagged Customer should not be charged tagged Shipping Method Fee #5950

Closed
emilyjeanrogers opened this issue Aug 27, 2020 · 4 comments
Closed
Labels
bug-s3 The bug is stopping a critical or non-critical feature but there is a usable workaround.

Comments

@emilyjeanrogers
Copy link

emilyjeanrogers commented Aug 27, 2020

Description

Customers are being charged shipping method fees when they should not be based on tag rules. They are not shown the fee in their cart, but it appears in the order confirmation screen after paying and is charged to their Credit Card.

The Enterprise has been contacted by 2 customers who have been charged shipping method fees when they are tagged as members and should not be charged those fees. The fees were not displayed in their cart, but did appear in their order confirmation screen after paying, and in their order confirmation emails.

Replicated as a test customer, screen grabs below. See error message under Shipping Info in Shopping Cart.

Expected Behavior

Shipping Method Fee should not be charged.
If Shipping Method Fee is charged, it should appear in cart total.

Actual Behaviour

Enterprise Willunga Farmers Market (2807)
A Shipping Method Fee of 10% is tagged non-member
Tag rule is set up that customers tagged member should not see shipping methods tagged non-member

EXAMPLE 1 - REAL CUSTOMER:

Customer for order R428222545 is tagged as member
Order Details on OFN and confirmation email to the customer both confirm that the total order is $137.44 and a $12.04 shipping fee was charged.
Customer says the shipping fee did not appear in their cart total, but it did appear in their order confirmation email.

EXAMPLE 2 - OFN TEST TRANSACTION on same Enterprise

Customer for order R126884235 is tagged as member

Cart total prior to Paying
Screen Shot 2020-08-27 at 10 58 14 AM

Order Confirmation after Paying
Screen Shot 2020-08-27 at 11 01 06 AM

Steps to Reproduce

Unable to replicate using a test account. Customer tagged member did not see, and was not charged the tagged shipping method fee.

CAN Replicate by creating a test customer for Willunga Farmers Market, tagging customer as member, and carrying out a test transaction in the shop.

Animated Gif/Screenshot

Workaround

No workaround. Member customers are being charged a fee that is a) not supposed to be charged to them and b) not appearing in their cart prior to confirmation of payment.

Severity

Your Environment

  • Version used:
  • Browser name and version:
  • Operating System and version (desktop or mobile):

Possible Fix

@emilyjeanrogers emilyjeanrogers added the bug-s1 The bug is stopping the platform from working, and there is no workaround. Impact of lot of users. label Aug 27, 2020
@mkllnk mkllnk self-assigned this Aug 27, 2020
@mkllnk
Copy link
Member

mkllnk commented Aug 27, 2020

I noticed that the enterprise has only one shipping method for customers tagged non-member. I would have thought that you need another (free) shipping method for members.

@mkllnk mkllnk added bug-s3 The bug is stopping a critical or non-critical feature but there is a usable workaround. and removed bug-s1 The bug is stopping the platform from working, and there is no workaround. Impact of lot of users. labels Aug 27, 2020
@mkllnk
Copy link
Member

mkllnk commented Aug 27, 2020

The problem is the missing shipping method for members. Creating a new shipping method tagged for members solves the problem. So this issue can be reframed as:

A missing shipping method due to tags selects the wrong shipping method during checkout and charges wrong fees

The system warns if you don't have a shipping method set up and doesn't show the shop as open (not ready for checkout). But this check seems to fail when there is a shipping method that can't be applied because of a tag rule.

@mkllnk
Copy link
Member

mkllnk commented Aug 27, 2020

I created the missing shipping method.

@kirstenalarsen
Copy link
Contributor

Seems like this has been solved and should be closed? @mkllnk @RachL Please reopen if I have this wrong

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug-s3 The bug is stopping a critical or non-critical feature but there is a usable workaround.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants