Shopify can require the shipping-address phone field when your delivery workflow needs a value. CartBlock can apply the currently documented phone operators to empty values, maintained placeholder values, or carefully reviewed text patterns. These checks do not prove that a number is valid, reachable, or owned by the shopper.

If presence is the only requirement, use Shopify’s native setting to make the shipping phone field required. This guide instead focuses on placeholder and value screening while preserving the limits of the verified CartBlock builder.

Verified September 21, 2026: CartBlock's Multiple Checkout Fields Validator lists Phone number with Is empty, Is not empty, Any, Not any, Partially contains, and Partially does not contains. The current builder does not show regex, length, prefix, suffix, country-aware formatting, or normalization controls for this field. It also does not label the phone source as buyer, shipping, or billing. Test the exact checkout paths your store uses.

What Shopify checkout phone number validation can check

Shopify checkout phone number validation checks whether a submitted phone value meets a store's documented rule. Depending on the tool, that can mean checking presence or rejecting known complete values or substrings. It does not, by itself, prove that the number works or belongs to the shopper.

Check What it proves Practical method
Presence A value was entered Shopify's required shipping phone setting or CartBlock Is empty
Format or plausibility The stored value meets a written pattern and is not a known placeholder Shopify's checkout parsing plus tested CartBlock exact or partial rules
Ownership or reachability The shopper controls a working number A separate OTP or phone-verification service

This guide focuses on the second check. A correctly formatted number can still be unreachable or belong to somebody else.

Before you create a phone validation rule

Write down why you need the phone number and which orders the policy covers. A carrier may need it for delivery updates, while a digital-only order may have no shipping-address step.

Choose a policy that your team can test. For example:

  • Require a shipping phone number for physical orders.
  • Accept international numbers after Shopify has parsed them.
  • Reject a maintained list of known placeholders, such as numbers used repeatedly in fraudulent or test orders.
  • Show a correction that tells the shopper what to enter.

Avoid a single local digit pattern for a worldwide store. Country calling codes and national number lengths vary. Spaces, parentheses, and a leading plus sign can also change what the shopper types without changing the underlying number.

How to set up Shopify checkout phone number validation

1. Require the shipping phone field when every shipped order needs it

In Shopify admin, go to Settings > Checkout. Under Customer information, set Shipping address phone number to Required, then save. Shopify documents these controls in its checkout form settings.

This native setting handles presence for checkout flows that include a shipping address. Shopify says these customer-information settings do not apply to B2B checkouts, so test B2B separately.

If your rule should apply only in selected situations, leave the native setting aligned with your broad store policy and use a conditional validation for the narrower case.

2. Open the CartBlock validation builder

In CartBlock, open Validation Rules, select Create, and choose Multiple Checkout Fields Validator.

CartBlock checkout validation can apply focused rules before an order is completed.

Give the validation an internal title that describes its purpose, such as Reject placeholder shipping phone numbers.

3. Add a Phone number rule

Open the Phone number field and select Add rules. Choose an operator that matches a behavior verified in the current builder:

  • Use Is empty to block a missing value under a conditional policy.
  • Use Any or Not any for a maintained list of complete values.
  • Use Partially contains or Partially does not contains only when the substring is safe across every supported market.

For example, a store that repeatedly receives the same normalized placeholder number can add that complete value to a disallowed list. A broad substring such as 000 can also appear inside a legitimate number, so do not block it without reviewing real order patterns and testing false positives.

CartBlock's current phone rule does not provide a regular-expression or digit-length operator. Do not paste a regex into a plain value field or promise arbitrary country-specific format enforcement from this builder.

4. Write a corrective checkout message

Tell the shopper what to fix without echoing their complete number:

Enter a complete phone number, including the country code, so we can contact you about delivery.

If the policy is country-specific, give a short accepted example for that market. Keep the message focused on correction; a format check does not verify that the number is active.

5. Save and activate the validation

Review the validation title, phone condition, scope, and error message. Save the rule and confirm that it is active before testing.

6. Test every checkout path

Run tests with a physical product and a real test destination. Include the checkout surfaces your customers use, especially Shop Pay or other accelerated checkout paths.

Phone validation test matrix

Test input or path Expected result
Empty shipping phone Blocked when the native setting or Is empty rule requires it
Valid domestic number Accepted after Shopify parses it
Valid international number with country code Accepted under an international policy
Spaces or parentheses Confirm the stored behavior in checkout rather than assuming normalization
Number on the maintained disallowed list Blocked with the corrective message
Similar legitimate number Accepted; proves the rule is not too broad
Digital-only cart Documented result when no shipping step appears
B2B checkout Tested separately because native customer-information settings differ
Shop Pay or another accelerated checkout Same intended outcome after its CartBlock checkout-block setup is verified

Record the exact input, market, device, checkout path, result, and rule version. Repeat the matrix whenever you change the disallowed list or expand into a new market.

Common phone validation mistakes

Treating required and valid as the same thing

A required field only proves that text is present. Keep the native presence setting and your plausibility rules as separate test cases.

Claiming regex support that the builder does not show

The verified CartBlock phone operators do not include regex. Use only the operators visible in your account and contact CartBlock support if your policy needs a capability the builder does not expose.

Blocking international shoppers with one local rule

A fixed length or prefix can reject legitimate international numbers. Scope country-specific policies by market only when the current builder and your tests support that setup.

Assuming a format check verifies ownership

Neither a required field nor a pattern check confirms reachability. Use a separate verification service when ownership matters to the transaction.

Skipping accelerated checkout tests

Shop Pay may require the CartBlock checkout block to be enabled for consistent behavior. Follow the owned Shop Pay setup guidance and test the live path.

Frequently asked questions

Can Shopify require a phone number at checkout?

Yes. Shopify can make the shipping-address phone number required for checkout flows that include shipping. This checks presence, not ownership.

Can CartBlock validate a phone number with regex?

The Phone number rule verified on September 21, 2026 does not show a regex operator. It shows presence, exact-list, and partial-text operators. Verify the builder in your account before designing a more complex format policy.

Does Shopify normalize phone numbers?

Shopify's Function API documents the deliveryAddress.phone value as E.164-formatted. That API documentation does not establish how CartBlock transforms or compares shopper input. CartBlock does not document a separate normalization control in its current phone-rule UI, so test what your checkout stores and passes to the rule instead of assuming how shopper-entered punctuation is handled.

Can phone format validation confirm that a number is real?

No. It can reject missing, malformed, or known placeholder values under the rules you configure. Confirming reachability or ownership requires a separate verification step.

Enforce the phone policy your store can support

Shopify checkout phone number validation works best when each rule has a narrow, testable purpose. Start with Shopify's required shipping-phone setting when every physical order needs a number. Then use CartBlock for focused rules that the current builder can express, such as rejecting a maintained list of known placeholders and showing a clear correction at checkout. Explore CartBlock on the Shopify App Store and test the rule with your markets and checkout paths before relying on it.