8000 Virtual orders still require an address (billing) - no option to make it optional? · Issue #39866 · magento/magento2 · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Virtual orders still require an address (billing) - no option to make it optional? #39866

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.

Sign up for GitHub

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

Jump to bottom
Open
5 tasks
ioweb-gr opened this issue Apr 26, 2025 · 2 comments
Open
5 tasks

Virtual orders still require an address (billing) - no option to make it optional? #39866

ioweb-gr opened this issue Apr 26, 2025 · 2 comments
Labels
feature request Progress: ready for grooming Reported on 2.4.x Indicates original Magento version for the Issue report. Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it

Comments

@ioweb-gr
Copy link
Contributor
ioweb-gr commented Apr 26, 2025 •
edited
Loading

Summary

We have bumped into a case where our customer is selling virtual items only in a rapid-commerce style. The user only needs to fill in minimal information like his email and phone to order the items.

What we've stumbled upon is the inability to disable requesting a full address.

When the order is virtual, correctly the shipping address disappears and becomes optional. However the billing address is still requested to checkout.

How can we solve this issue to make both addresses optional? Is there a way to manage this use-case?

Examples

Think of products with serial numbers. In order to deliver the item, you only need the customers' email or his phone number.

Currently a full address is required to submit the order.

Proposed solution

It would be great if we could have an option in the backend for adjusting whether billing address is optional for virtual orders.

Release note

No response

Triage and priority

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
@ioweb-gr ioweb-gr added the Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it label Apr 26, 2025
@m2-assistant M2 Assistant
Copy link
m2-assistant bot commented Apr 26, 2025

Hi @ioweb-gr. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

@github-project-automation github-project-automation bot moved this to Ready for Confirmation in Issue Confirmation and Triage Board Apr 26, 2025
@engcom-Bravo engcom-Bravo added the Reported on 2.4.x Indicates original Magento version for the Issue report. label Apr 29, 2025
@engcom-Bravo
Copy link
Contributor

Hi @ioweb-gr,

Thanks for your reporting and collaboration.

We gone through with the description and it seems to be and Enhancement to proceed further marking this as Feature Request

Thanks.

@engcom-Bravo engcom-Bravo moved this to Ready for Grooming in Feature Requests Backlog Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request Progress: ready for grooming Reported on 2.4.x Indicates original Magento version for the Issue report. Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Projects
Feature Requests Backlog
Status: Ready for Grooming
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ioweb-gr @engcom-Bravo
0