Domain Sales Manager turns a WordPress site into a focused storefront for a portfolio of domain names. It stores the inventory in WordPress, renders sale cards with a shortcode, uses WooCommerce for payment tracking, and can route higher-value transactions to Escrow.com. A dependable launch takes more than uploading a ZIP: the pricing threshold, payment paths, inventory states, form behavior, and post-payment handoff all need to agree.
Decide how each sale should move before installing
Start by drawing the two transaction paths. Lower-priced names can use a supported WooCommerce gateway and its secure order-pay screen. Names above the direct-payment maximum can be sent to Escrow.com. That threshold is a business control, not just a technical setting. Choose it with transaction risk, payment limits, refund handling, and your internal approval process in mind.
WooCommerce is required. Direct checkout also needs at least one gateway supported by the plugin and enabled in WooCommerce. The current product supports PayPal Payments, Zelle, and Cash App in its gateway allowlist. Escrow checkout needs a separate Escrow.com account, account email, and API key. Contact Form 7 is optional when you want an inquiry or make-offer form inside a domain card. GTranslate and DynoReg Custom Currencies are optional integrations and should be installed only when they serve a real requirement.
Prepare a safe WordPress installation
- Confirm that WordPress, WooCommerce, PHP, the active theme, and the intended payment extensions are current and compatible.
- Back up the database and files, then make the first installation on a staging copy when the site already takes live orders.
- Download the purchased plugin package from CodingRepo and keep the original archive in a controlled location.
- Install and activate WooCommerce first. Configure currency, taxes where applicable, customer emails, payment gateways, and HTTPS before adding the domain workflow.
- In WordPress, go to Plugins, choose Add Plugin and Upload Plugin, select the Domain Sales Manager ZIP, install it, and activate it.
- Review the new Domain Sales administration area before publishing any shortcode. Do not expose a fallback domain or a live purchase button until the settings have been tested.
Configure the transaction rules
Set the site-wide default card theme, direct-payment maximum, allowed query-string keys, optional fallback domain, and any custom CSS. Keep query keys short and intentional. The defaults can include domain, d, and slug, which makes it possible for one landing page to show different inventory records. If that routing is used in advertising or email, test every generated URL and define what should happen when a value is missing or invalid.
Enable only payment gateways that are already working in WooCommerce. A direct transaction creates a dynamic WooCommerce order rather than a separate product post. The plugin reserves the domain before checkout, marks it sold when the order reaches Processing or Completed, and releases the direct-payment reservation when an order fails or is cancelled. Your team still needs a documented procedure for abandoned Pending or On-hold orders and for confirming the registrar transfer.
Configure Escrow.com in sandbox first. Verify the seller identity, currency, inspection period, price, and API endpoint. A successful request creates a transaction and records its identifier on an on-hold WooCommerce tracking order. In the current product, Escrow completion, cancellation reconciliation, and the registrar transfer are operational steps; they are not automatically completed by the plugin. Assign an owner for those steps before enabling production Escrow transactions.
Build domain inventory that cannot be misunderstood
Create a small pilot set before importing or entering the complete portfolio. For each domain, verify the exact name, slug, price, currency, status, active state, headline, description, button text, theme override, and optional Contact Form 7 selection. Use Available for a fixed-price name that can be purchased, Make offer when the next step is a conversation, Reserved while a transaction is legitimately in progress, Sold only after the business criteria are met, and Hidden when the record must not appear.
Keep sales copy factual. A domain description should not promise trademark clearance, search performance, traffic, or a particular resale value unless those claims have been independently substantiated. Explain what is included in the purchase and when the buyer will receive transfer instructions. The plugin does not add registrar APIs, WHOIS lookup, automatic DNS verification, or automated transfer completion, so those responsibilities need a separate operating checklist.
Place and test the sale card
Create the intended WordPress page and insert the [domain_sale] shortcode. Select a record explicitly by ID, domain name, or slug when the page belongs to one domain. Use query-string routing only for a carefully tested shared landing page. Check the clean, dark, premium, and minimal presentations against the active theme, including keyboard focus, responsive wrapping, error messages, and the optional inquiry form.
Run end-to-end tests before advertising the page:
- Open an available fixed-price domain and confirm its displayed price and currency match the admin record.
- Start a direct checkout in the gateway’s sandbox or test mode, confirm the exact domain appears in the order, and test success, failure, and cancellation states.
- Start a high-value sandbox transaction and confirm the Escrow.com transaction data and WooCommerce tracking order are correct.
- Test a Make offer record and verify the selected contact form, notifications, spam protection, and privacy notice.
- Check reserved, sold, hidden, inactive, missing, and invalid-route cases so none accidentally presents a purchase action.
- Repeat the checks on desktop, tablet, and mobile, and inspect the WordPress and WooCommerce logs without placing credentials or buyer data in shared reports.
Plan the operating handoff
Document who can change prices, release reservations, reconcile WooCommerce and Escrow records, communicate transfer instructions, and mark a name sold. Restrict WordPress administration to the people who need it, protect Escrow credentials, use tested backups, and schedule a periodic inventory review. A polished card cannot compensate for a stale availability state or an unclear transfer process.