Marcus Reyes
Supply Chain & Inventory Specialist | 12 Years
Marcus has managed supply chain and inventory operations in food & beverage manufacturing for over a decade, with a focus on compliance, lot traceability, and waste reduction. He has worked with FDA-regulated manufacturers across the US.
A supplier gets a purchase order from "noreply@somesystem.com" and does one of three things: ignores it, marks it as spam, or replies "who is this?" back into a mailbox nobody reads. None of those outcomes are what you wanted when you hit send. This is one of the most common, least discussed friction points in purchasing — the software works fine, the PO is accurate, and it still doesn't land the way it should, because of the address it came from.
The Problem with System Addresses
Most inventory and purchasing software sends transactional email — purchase orders, sales quotes, order confirmations — from a shared system address, something like noreply@vendorplatform.com. That address is used by thousands of other companies running the same software, and mail providers know it. Spam filters score bulk-sender domains more aggressively than a company's own verified domain, so a PO that would sail into a supplier's inbox from your own domain can land in their spam folder or a "clutter" tab that they only check once a week, if that.
Even when it does land in the primary inbox, a "noreply" address confuses the reply workflow. Suppliers routinely have questions on a PO — a quantity that looks off, a delivery date that needs confirming, a price they want to clarify before confirming. If they hit reply and it bounces, or worse, disappears into a monitored mailbox nobody actually checks, that question sits unanswered while your order sits unconfirmed. You find out three days later when you follow up, and the whole cycle restarts.
There's also a quieter cost: brand trust. A purchase order is a legal-ish business document — it has your company name, your terms, your signature block. When it arrives from a generic system domain instead of yours, it reads a little like a phishing attempt, or at minimum like a smaller, less established operation than you actually are. Suppliers who deal with dozens of buyers notice which ones send from their own domain and which ones don't, and it shapes how seriously they take the relationship.
How Domain Authentication Works, in Plain English
The fix isn't complicated, but it does involve a bit of behind-the-scenes proof. Email systems don't just trust that a message claiming to be from purchasing@yourcompany.com actually came from you — anyone could type that address into the "From" field. To prevent that, receiving mail servers check a small set of DNS records published on your domain that act like a signed authorization list.
Three records typically do this work:
- SPF — a DNS record listing which mail servers are allowed to send email claiming to be from your domain.
- DKIM — a cryptographic signature attached to outgoing mail that proves it wasn't altered in transit and really did originate from an authorized sender.
- DMARC — a policy record telling receiving mail servers what to do if a message fails those checks (reject it, quarantine it, or just report it).
None of this changes your regular inbox or how your team sends everyday email. It's a narrow, additive step: you're telling the internet "this specific sending service is also allowed to send mail as my domain," for purchasing and quoting purposes specifically. Once the records are in place and verified, mail servers on the receiving end trust that a PO from purchasing@yourcompany.com is legitimately from your company, and treat it accordingly — better inbox placement, no spam warnings, and a reply-to address suppliers actually recognize.
What the Setup Looks Like in Nstock
Nstock handles this under Settings → Email Sending. The flow is designed to take a few minutes of active work, even though the DNS propagation afterward can take longer:
- Add your domain (e.g., yourcompany.com).
- Nstock generates the SPF, DKIM, and DMARC records you need and shows them to you as plain text.
- Copy those records into your domain registrar's DNS settings (GoDaddy, Namecheap, Cloudflare, wherever your domain is managed).
- Click Verify in Nstock. It checks whether the records are visible and correctly formatted.
- Choose a send-from address on your verified domain — commonly something like purchasing@yourcompany.com.
Once verified, purchase orders and sales quotes automatically send from that address instead of the default system sender. If a domain isn't configured, or verification hasn't completed yet, Nstock falls back safely to the default sender — nothing breaks and no email fails to send while you're mid-setup.
This is a Business plan feature, available as an add-on on lower tiers. See pricing for current plan details.
Troubleshooting
DNS changes aren't instant. Records can take anywhere from a few minutes up to 24-48 hours to propagate fully across the internet, depending on your registrar and existing DNS settings, so a failed verification right after adding records isn't necessarily a mistake — it may just need time.
If verification still fails after a day or two, the most common culprit is a record copied with a typo, extra whitespace, or missing quotation marks where the registrar's interface expects an exact string. Compare what's published in your DNS settings character-for-character against what Nstock generated. The Verify button re-checks live DNS at any time, so once you've fixed a record you can re-run it immediately rather than waiting for another propagation cycle. Full setup steps are documented in Help.
Frequently Asked Questions
Does this affect my regular email? No. Domain authentication for sending only adds an authorized sender for purchasing and quoting mail — it doesn't touch your team's mailbox, your regular company email, or any other mail flow. It's purely additive.
What addresses can I use? Any local part on your verified domain — purchasing@, orders@, procurement@, or a specific buyer's name @yourcompany.com. Once the domain itself is verified, you can pick whichever address makes sense for how your team wants suppliers to reply.
Is this included in the trial? No. Custom domain sending is a Business plan feature or a paid add-on on other plans — it's not part of the free trial. See the Domain Authentication entry in the glossary for a fuller technical definition, or check pricing for plan specifics.
Suppliers respond faster and take your purchasing more seriously when a PO arrives from an address that's clearly yours. It's a small setup step with an outsized effect on how quickly your orders actually get confirmed — and it matters most for suppliers you've deliberately chosen to work with long-term. If you're not there yet with a given supplier, vetting them first with an RFI, RFP, or RFQ is worth doing before the relationship becomes routine enough that domain setup is worth the effort.