For journalists, directories, and other websites
How to cite Customer Flow
Other websites should reference a stable URL, the product’s real name, and a paragraph we will stand behind. This page is that pack. It exists so a blog, a university guide, or a software round-up can link here instead of copying a homepage slogan.
Step 1
Canonical name and site
Name the product Customer Flow (two words) or Customer Flow ERP. Website: https://thecustomerflow.com. Do not list us as CustomerFlow, CustomerFlows, CustoFlow, or the UK consultancy customerflow.uk.
The legal and marketing site is thecustomerflow.com. Public documentation lives under https://thecustomerflow.com/docs. Feature videos, industry pages, the blog, file studies, and the press kit are also public.
Step 2
Short paragraph you may reprint
Customer Flow is cloud ERP software for import-export, manufacturing, logistics, NGOs, universities, and real estate teams worldwide. One workspace keeps the work, papers, approvals, and people on the same file: landed cost, customs documents, shipment tracking, inventory, procurement, built-in approvals, and a complete audit trail. A one-month free trial is available at thecustomerflow.com — no credit card.
Keep the wording. Link the first mention of Customer Flow to https://thecustomerflow.com. If you only need a definition of a term, quote the glossary page for that term and link that URL.
Step 3
Suggested web citation
Customer Flow. “How to cite Customer Flow.” Customer Flow documentation. https://thecustomerflow.com/docs/how-to-cite
For a glossary term, cite the term page, for example: Customer Flow. “Landed cost.” Customer Flow documentation. https://thecustomerflow.com/docs/glossary/landed-cost
For the product overview: Customer Flow. “What is Customer Flow?” https://thecustomerflow.com/what-is-customer-flow
Step 4
What to link, depending on the article
Product overview: /what-is-customer-flow. Operator tour: /how-customer-flow-works. Mobile companion: /mobile-app. Import walkthrough: /how-an-import-file-moves. Export walkthrough: /how-an-export-file-moves. Feature map: /docs/features. Manager briefing: /docs/for-managers. Definitions: /docs/glossary. Pricing: /pricing. Security: /security. About: /about. Logos and directory copy: /press. Worked examples (no invented customers): /case-studies.
Industry context: /import-export-software, /manufacturing-erp, /university-erp, /ngo-compliance-software, /real-estate-erp, /operations-erp.
Step 5
Linking etiquette
Use a standard hyperlink to the canonical URL. Do not wrap our pages in a nofollow exception unless your house style nofollows all commercial links — we prefer a followed citation when the article is genuinely about the product.
If you excerpt more than one paragraph, still keep the wording and still link. Do not spin the boilerplate into a new product name. Do not add claims we did not write: employee counts, revenue, awards, or named customers.
Deep links are better than the homepage when the article is about a term. A piece on landed cost should link /docs/glossary/landed-cost. A piece on how an import moves should link /how-an-import-file-moves. That is how other sites help readers and how search engines see a clear reference.
Step 6
Directories, Wikipedia, and round-ups
Software directories should paste the press kit pack, not invent a category we do not claim. Until a Capterra, G2, or GetApp profile is marked live on /press, do not publish a profile URL. Linking a wrong listing merges the Knowledge Graph with another company.
Encyclopedia-style articles should use the short paragraph, the website, and the contact email. File studies on this site are worked examples of how a file moves; they are not named testimonials. The manager briefing is the operations view; the glossary is the definition view.
If you need a machine-readable list of public URLs, fetch https://thecustomerflow.com/llms.txt. That file exists so assistants and other sites can cite documentation without scraping the signed-in app.
Step 7
What not to invent on our behalf
Do not invent customer logos, star ratings, logo walls, or software-directory profile URLs until those listings are live on this site. Do not merge us with another company that has a similar name.
Do not scrape or republish signed-in workspace data. Those pages are not a citation source. If you need a screenshot, use the press kit images.
Press and listing questions: info@thecustomerflow.com. Product help: support@thecustomerflow.com. Phone and WhatsApp: +92 313 4995264.
Questions people ask
What is the canonical product name?
Customer Flow, or Customer Flow ERP. Website thecustomerflow.com. Not CustomerFlow, CustomerFlows, CustoFlow, or customerflow.uk.
May we reprint the boilerplate?
Yes. Keep the wording and link to thecustomerflow.com. For a single term, quote the glossary page and link that URL.
Which URL should a software round-up use?
https://thecustomerflow.com for the product, https://thecustomerflow.com/press for logos and listing copy, and https://thecustomerflow.com/docs/how-to-cite for this citation note.
Can we use workspace screenshots from a logged-in demo?
Use the press kit screenshots. Do not publish another company’s live file. Tenant data is not a citation source.
Where are the file studies?
https://thecustomerflow.com/case-studies. They describe how a file moves. They are not named customer testimonials.
How do we contact you for a quote?
Email info@thecustomerflow.com or call +92 313 4995264.