.market vs .shop vs .store: Which Domain Fits the Business?

Choose .market when the website brings together sellers, buyers, listings, data, or participants in a venue. Choose .shop when the name should read like an invitation to browse and buy. Choose .store when the website is the branded retail destination for one merchant or product catalog.

The distinction is about the business model, not technical capability. All three can run an online shop, marketplace, publication, landing page, or redirect. The stronger domain is the one that sets the right expectation before the visitor sees the interface.

1) Define who sells

Start with the commercial relationship. A marketplace normally hosts offers from several independent sellers or connects distinct participant groups. A store normally sells its own inventory, or presents one merchant as the contractual seller. A shop can describe either, but customers often read it as a direct retail proposition.

Write down the answer to five questions:

1. Who owns or supplies the goods or services?
2. Whose name appears as the seller at checkout?
3. Who processes or receives the payment?
4. Who fulfils the order or booking?
5. Who handles returns, disputes, guarantees, and support?

If different sellers answer those questions for different listings, .market can describe the venue accurately. If one brand is responsible throughout the transaction, .store or .shop is usually clearer.

Hybrid models need an explicit choice. A retailer that adds third-party sellers may keep a store identity while explaining the marketplace program. A marketplace that launches its own private-label products should distinguish “sold by the platform” from independent listings. The domain cannot repair a blurred seller relationship.

2) Read each word literally

“Market” has several durable meanings: a physical or local market, a multi-seller venue, a B2B exchange, a category of buyers, a market-data publication, or a place where assets are traded. That breadth helps a platform with several transaction types, but it can be vague for one merchant.

“Shop” functions as both a noun and a verb. brand.shop can read as a store name or as an instruction to shop the brand. It suits short direct-response names, creator merchandise, product launches, and campaigns. The action-oriented tone can feel less natural for wholesale procurement, professional services, or a neutral exchange.

“Store” usually describes a destination or catalog. brand.store says where the brand's products are sold. It is a strong fit for a retailer, manufacturer, publisher, game studio, artist, or software company with a defined merchandise operation.

Read the complete candidate, including the words before the dot. Avoid repetition such as harbormarket.market, cedarshop.shop, or northstore.store unless the repeated brand is already established and the full name still tests well.

3) Match the customer journey

The extension should predict the first useful action.

Use .market when visitors are likely to:

• compare several sellers or listings;
• post a request or offer;
• discover a local market and its vendors;
• browse supply and demand;
• review market data or research; or
• participate in an exchange, auction, or booking venue.

Use .shop or .store when visitors are likely to browse one merchant's catalog, add products to a cart, book the brand's service, or buy official merchandise.

Map the first five screens from landing page to confirmation. If the domain says “market” but every product is sold by one company, the broader label may create questions without adding value. If the domain says “store” but checkout changes sellers, policies, delivery promises, and support channels by listing, the apparently simple retail label may hide material differences.

Test names with realistic tasks. Ask participants who they think the seller is, where they would seek a refund, and whether they expect several vendors. Their answers reveal a semantic mismatch that a memorability survey may miss.

4) Show seller identity

Commerce trust depends on knowing who is responsible. A marketplace should identify the platform operator and make the seller for each listing visible before payment. A direct store should identify the merchant legal entity and keep it consistent across product pages, checkout, receipts, statements, and support.

Publish the details required for the relevant markets, products, and customer types. These may include:

• legal and trading names;
• business and tax registration details;
• physical and service addresses;
• seller contact information;
• product origin and condition;
• price, currency, tax, shipping, and fees;
• return, cancellation, warranty, and dispute terms;
• marketplace ranking or sponsored-listing disclosures; and
• regulated permissions for relevant goods or services.

Do not let a polished domain imply that the platform has inspected every seller or product unless the process and limits support that claim. Terms such as “verified,” “certified,” “official,” and “guaranteed” need precise definitions, evidence, and review.

5) Separate platform roles

A marketplace can provide discovery, messaging, payments, logistics, insurance, financing, dispute handling, or fulfillment. The platform may perform some roles directly and contract others to vendors.

Create a responsibility matrix for each transaction stage:

Put the relevant answer near the decision, not only in a general terms page. If roles change by category or country, state the variation where it affects checkout.

A .shop or .store site can also host third-party products, but the direct-retail language raises the need for clarity. Customers should not have to infer a hidden marketplace structure from a seller name in small type.

6) Plan the product scope

Choose for the roadmap, not only the launch inventory.

.market leaves room for new sellers, categories, locations, service providers, auctions, requests, and research. That flexibility is useful when the core product is exchange or discovery. It can be too broad when the company wants customers to remember one product brand.

.shop works well for a focused commerce experience, seasonal campaign, creator storefront, or direct-response landing name. A business that expects wholesale operations, subscriptions, services, or software may need a broader parent domain.

.store comfortably covers a growing product catalog and official merchandise. It can sit under a broader company architecture, such as a retail destination linked from a parent .com.

Possible structures include:

Keep one canonical page for each listing, product, policy, and article. Duplicate stores split inventory, reviews, analytics, links, and policy updates.

7) Handle sensitive markets

“Market” can refer to securities, foreign exchange, commodities, prediction markets, property, employment, health products, or other regulated and high-consequence categories. The extension does not authorize an exchange, broker, platform, product, promotion, or transaction.

Before using .market for a sensitive category, identify:

• the operator and contracting entities;
• every target jurisdiction;
• whether the platform executes, arranges, advises, advertises, or only publishes data;
• applicable licences, registrations, exemptions, or prohibitions;
• required risk and advertising disclosures;
• customer eligibility and location controls; and
• how users verify the operator with an official authority.

Avoid names that imply an official exchange, guaranteed liquidity, regulatory approval, or government status without direct support. The same caution applies to health, alcohol, weapons, age-restricted goods, tickets, property, and employment listings.

For a finance-category product, the finance comparison explains why the domain and regulated permission must remain separate.

8) Keep search claims accurate

IANA's %%EDITORIAL_0%% record classifies it as a generic TLD sponsored by Dog Beach, LLC in the Identity Digital registry family. It records registration on 22 May 2014, transfer to the current sponsor in 2021, and an update on 7 October 2025.

ICANN's registry agreement is dated 6 March 2014. These records establish the namespace and operator relationship. They do not restrict .market to a specific commercial model or validate a merchant.

Google's current search FAQ says the TLD does not determine search performance. None of the three endings receives an automatic ranking advantage for shopping or marketplace queries.

Use the extension for clarity and naming. Search performance still depends on useful category and product pages, unique listing information, accessible navigation, stable URLs, structured data that matches visible content, reputation, links, and many other factors.

9) Compare current prices

Prices were checked on 16 August 2026 for standard, non-premium names.

Porkbun's pricing table includes fees and shows .market at $35.53 for registration, renewal, and transfer. It shows .shop at $2.06 first year and $31.41 renewal, and .store at $2.57 first year and $43.77 renewal. The calculated three-year totals are $106.59, $64.88, and $90.11.

Namecheap %%EDITORIAL_0%% displays $46.98 first year, $55.98 renewal, $46.98 transfer, and $140.94 for a three-year registration purchase. Its %%EDITORIAL_5%% page displays $0.98 first year and $78.94 for three years. Its %%EDITORIAL_8%% page displays $0.98 first year and $89.74 for three years. A $0.20 fee may apply to affected transactions.

Displayed multi-year registration prices are not always the same as one promotional year plus ordinary renewals. Compare the actual term in checkout, ordinary renewal after that term, premium status, fees, tax, privacy, email, and recovery cost. Recheck every price before publication or purchase.

10) Test the full name

Compare obtainable names, not abstract extensions. A short, exact .store can beat a long .market modifier, while a distinctive .market can explain a platform better than a compromised .shop.

Test each candidate in:

• the browser address bar;
• search results and ads;
• product and listing URLs;
• email addresses and support scripts;
• app-store and social profiles;
• packaging, receipts, and statement descriptors;
• radio, video, and spoken referrals; and
• common typo and .com assumptions.

Use Bulk Search to compare the complete shortlist together. Then use domain research for registered candidates and review trademark, company, marketplace, social, and historical-use records.

If the exact .com is taken, compare a durable modifier, an accurate commerce TLD, a country-code option, or controlled acquisition. The taken-domain guide provides a decision path without assuming the listed resale price is justified.

11) Apply the choice

Choose .market when the venue or exchange is the product, several sellers or participants are central, or the site covers a market beyond direct retail. Make operator and seller roles explicit.

Choose .shop when the name should feel active, approachable, and transactional. It is especially useful for a short campaign, creator shop, direct-to-consumer offer, or brand phrase that reads naturally with “shop.”

Choose .store when the site is the official destination for one merchant's catalog or a clearly defined retail division. It offers a direct description without the multi-seller implication of “market.”

Own more than one when customer error, brand protection, or future architecture justifies the renewal cost. Select one canonical destination and redirect the others. Do not operate duplicate catalogs or policy pages.

The extension should state what the customer is entering. The seller model, checkout evidence, remedy, product scope, and complete name decide whether that promise remains accurate.