Shopify Customer Accounts Explained: New Accounts, Classic Accounts, and What Actually Changes
First, check the fulfillment status
Everything about this request depends on one fact: has the order shipped yet. If it is unfulfilled, you have options. If it is fulfilled or in transit, you are no longer editing an order, you are arranging an exchange, and the conversation with the customer changes completely. Check the order timeline before you promise anything, because the wrong promise here creates the refund dispute you were trying to avoid.
In the Shopify admin, open the order and look at the fulfillment status first, the payment status second. An unfulfilled, paid order is the easy case. A partially fulfilled order means some items can still change and some cannot, which you need to explain clearly. Train whoever answers customer messages to check this before typing a reply; most bad outcomes in this scenario come from promising an edit that was never possible.
When you can edit the order
For unfulfilled orders, Shopify lets you edit: add or remove line items, change quantities, and adjust the order total, with the customer charged or refunded the difference. This is the cleanest path when the customer wants a different size or color of the same product. Make the edit, confirm the new total with the customer in writing, and note that the edit itself is the confirmation; do not also send a separate "we changed it" email that confuses the thread.
Edits have limits worth knowing. You cannot change the order into something unrecognizable without confusing your own records, and editing does not work once fulfillment has started. If the price difference is significant, get explicit approval before charging the extra amount; an unexpected charge on a card is how a simple size swap becomes a chargeback.
When to cancel and reorder instead
Cancel and reorder is the right call when the change is extensive (half the items are different), when the customer wants to add items that change shipping weight or method, or when the original order is already fulfilled. It is also cleaner when the customer is clearly unsure; a fresh order with a fresh confirmation beats three rounds of edits that nobody can follow.
The mechanics matter: cancel the original, issue the refund promptly, and create the new order, ideally as a draft order you send for the customer to approve and pay. Do not cancel without the replacement ready, or the customer experiences it as "my order was cancelled" rather than "my order was fixed." Speed of the refund is the whole ballgame here; a same-day refund turns a hassle into a loyalty moment.
What to tell the customer
The message template that works: confirm what you are doing, state the timeline, and name the money. "I have updated your order to the blue in size medium. The $12 difference has been refunded and should appear in 3 to 5 business days. Your order still ships Thursday." Every element answers a question the customer would otherwise ask in a follow-up message, which is the real cost driver in these exchanges.
If you cannot do what they asked, say so in the first sentence and offer the alternative immediately. "That order already shipped this morning, so I cannot change it, but here is what I can do: refuse the delivery or send it back with this prepaid label, and I will ship the correct item today." Bad news first, solution second, no hedging in between.
Preventing it next time
A sizing chart linked at the point of size selection, a clear "final sale" flag on items that cannot be changed, and an order confirmation email that arrives within minutes all reduce these requests. The confirmation email is the cheapest intervention: customers who catch their own mistake within the hour are easy to help, while customers who notice three days later are not.
Track how often this happens and why. If size swaps dominate, your size guide is failing. If customers keep adding forgotten items, your checkout may be rushing them. The pattern in the requests is free product-page research, and merchants who read it stop answering the same email every day.
The change in one paragraph: passwords are gone
Shopify new customer accounts replace the classic email and password login with a one time code sent to the customer email, tied to a Shop identity where the customer has one. No password to forget, reset, or reuse from a breached list somewhere else, which removes a whole category of support ticket and a real slice of account takeover risk. The classic accounts remain available, and stores choose which system their storefront uses.
That trade sounds pure until you run a store on it. Shared family emails, customers who shop from a work inbox they cannot receive codes at midday, older customers for whom a six digit code flow is a new trick: the friction did not vanish, it moved. Support teams feel the move first, in tickets that read locked out but mean code delayed, filtered, or sent to an address the customer checks weekly.
What the store gains, honestly itemized
A login that matches how customers already authenticate everywhere else, an account page Shopify maintains and extends, and a cleaner path into Shop Pay and Shop identity, where saved details lift checkout conversion for the customers who use it. For B2B, new accounts are the required road: company profiles, catalogs, and staff permissions hang off the new system, so a wholesale ambition settles the question by itself.
The account page also becomes Shopify surface rather than theme surface. Customization is narrower, branding controls are improving but bounded, and any store that built a beloved custom account dashboard in the classic world should inventory it before switching, because pieces of it will not come across.
What breaks or bends: apps and edge cases
Classic accounts carried years of app ecosystem: loyalty, subscriptions, and account page widgets that injected into theme templates the new system does not expose the same way. The major apps have been rebuilding for the new accounts with customer account extensions, but rebuilding is not identical, and a store should test its specific stack in a development store rather than trust a compatibility badge. Order history migration and customer recognition are handled by Shopify; the app behaviors are the store problem.
Edge cases cluster around identity. A customer with three emails across five years is three customers in the data until they are merged by behavior, not by settings. Guest checkout history does not retroactively attach because someone created an account later with a different address. None of this is a reason to stay classic forever. All of it is a reason to switch on a quiet Tuesday with support briefed, not during a sale.
The decision, in operator terms
If you sell B2B or plan to, switch, because the features you need only exist on the new system. If your customers are repeat retail buyers on mobile, the code flow plus Shop identity is likely a net win measured in completed logins. If your base skews older, buys by phone and email, and leans on accounts for standing orders managed by your staff, test carefully and keep the classic system until the code flow stops generating tickets.
Either way, measure the thing itself: login success and account related tickets for sixty days after the change. Accounts are plumbing. The right verdict on plumbing is a number, not a preference.
Related reading
If this topic is useful, these earlier guides go deeper on connected questions: Shopify Shipping Zones Explained: Rates, Regions, and the Settings That Cause Surprise Costs, Shopify Abandoned Checkouts Explained: Recovery Emails, Timing, and What the List Actually Means, and Shopify Taxes Explained: Nexus, Rates, and What the Platform Does Not File.
Frequently asked questions
Do customers need a Shop account to use new customer accounts?
No. The new accounts send a one time code to the customer email address, which works whether or not the customer uses Shop. Customers who do have Shop identity get a smoother sign in because their details are already saved there.
Can I switch back to classic accounts after moving?
Shopify has allowed stores to move between account versions, but the practical answer is to treat the switch as one way for planning purposes: app setups, customer communications, and support scripts all change, and flipping back and forth confuses customers most of all.
What happens to existing customer passwords when I switch?
They stop being used. Customers sign in with an emailed code under the new system, so there is nothing to migrate and nothing for customers to reset. Expect a short wave of confused regulars and brief support before the switch, not after the first complaint.
Do new customer accounts work for wholesale?
Yes, and they are the required foundation for Shopify B2B features like company accounts, catalogs, and payment terms. A store planning wholesale should plan the account switch as part of the same project, not as an afterthought.