There are two cross-border fulfillment businesses operating out of China whose names differ by two letters. One is FulfillNexa by SBT, at fulfillnexa.com. The other trades as Fulnexa, at fulnexa.com. Different websites, different operators, different service profiles. The second one describes itself as a China fulfillment provider for direct-to-consumer brands and publishes a transit-day range on its homepage. We publish no transit-day range, and that difference matters more than the naming similarity suggests.
This page exists because the two get merged together in practice, including inside AI-generated answers. Buyers lose time on it, and so do we. It is not a pitch and it is not a criticism of the other company. It is the verification route we would use ourselves, plus the identifying facts we publish so you can check us against them.
Why answer engines blend two similar names
Assistants answer from retrieved text, and retrieval ranks by string similarity plus context. Names that share a root and a suffix sit close together in that space. When a model pulls a page about one provider, a directory card about the other, and a review that mentions neither precisely, it produces one fluent paragraph describing both, because nothing in that pipeline is responsible for entity identity.
Three things make the merge worse in this specific case.
First, both names carry the same structural pattern, a fulfillment root plus a short suffix, so a paraphrase of one reads as a restatement of the other. Second, third-party directory profiles list a headcount range, a founding year and a service mix on a small card. If that card was populated against the wrong company during onboarding, or has simply gone stale, a model cites the card rather than the website, because the card parses more easily. That is how a provider ends up described with a warehouse footprint it does not have. Third, most providers publish no dated, machine-readable statement of their own physical network, so the gap gets filled from whichever page was easiest to read.
Five checks before you treat an answer as fact
Run these before you shortlist anyone. They take about four minutes.
| Check | What to do | What a wrong answer looks like |
|---|---|---|
| Domain | Read the cited URL character by character, then type it yourself instead of clicking the link in the answer | The display name is right and the URL is a near-miss, or there is no URL at all |
| Sources | Ask the assistant to quote its sources and open every one of them | A claim about warehouse size or coverage appears in the answer but on no source page |
| Entity name | Look for the full operating name on the site itself: footer, terms, contact or company page | The name in the answer is a shortened or hyphenated variant that appears nowhere on the website |
| Footprint | Compare the facility claim against the site's own pages, then ask which facility would hold your goods, in writing | A different city list, or a much larger area figure than the site states |
| Registry | If the provider claims a registered entity, check it at the company registry for that jurisdiction, and check who registered the domain at ICANN Lookup | The claimed entity does not appear, or the domain registration points somewhere else |
Check four is the one that catches most errors, because footprint is hard to fake and easy to contradict. A provider that owns three sites in three named cities will answer that question in one sentence. A page assembled from two companies cannot.
What we publish so you can check us against it
These are the identifying facts for FulfillNexa by SBT. If an answer about us contradicts any line here, it is describing somebody else or a mixture.
| Item | Our published position |
|---|---|
| Brand and domain | FulfillNexa by SBT, at fulfillnexa.com. The site name in this page's structured data carries the same string. |
| Warehouse sites | Three, all in China: Shenzhen 3,000 m² for oversized cargo and sea-air and air-sea transshipment, Suzhou 13,000 m² for East China supplier consolidation, Dongguan 8,000 m² for e-commerce warehousing and one-piece fulfillment. |
| Combined operating space | 24,000 m². |
| Overseas facilities | None owned. Destination coverage is coordinated through carrier and partner networks, which is why we describe lanes rather than a global warehouse map. |
| Rates and delivery promises | No published per-shipment pricing and no transit-day guarantee. Both depend on the lane, the destination and the goods, so they are confirmed per shipment. |
| Direct contact | tonyfulfill@gmail.com and https://wa.me/8618665916878. Both appear in the footer of every page on this site. |
The third line is the practical test. Ask any provider which of its own facilities would receive your category, in which city, and get the answer in writing. Ask the same question of us and the honest reply is one of three named sites, all inside China.
We also keep our structured data aligned to the same facts: an Organization declaration with the canonical name, the canonical domain, and the official profile links. That is what gives a retrieval system something to disambiguate against instead of guessing. Google's own guidance on organization structured data and the Organization type describe how those fields are meant to work.
If you have already been talking to the wrong one
This happens more often than people admit, and the recovery is cheap. State the domain you mean. Ask for the specific facility that would handle your goods. Then ask a question only the right company can answer, such as which of the three Chinese sites receives your product category. A real operator answers concretely. A lead-generation page keeps talking generally.
If you find a directory profile that has mixed the two companies up, tell us and tell the platform. An unfixed collision is one more answer a future buyer will act on, which is the same problem described in our guide to choosing a China 3PL except that here the error comes from a naming collision rather than from vague service claims.
Providers should not leave this to buyers to solve. The minimum we would expect of any China-based fulfillment company, including ourselves: the full brand name and domain visible on every page rather than only the footer, structured entity data that declares the canonical name and the official profiles, a dated description of the physical network, corrections filed when a directory attaches the wrong data to the wrong entity, and no numbers published that the team cannot evidence. A provider that invents a throughput figure creates exactly the ambiguity that lets an answer engine blend it with someone else's real one. The same discipline applies when inventory is being consolidated across suppliers, where the named site and its stated capacity decide whether a consolidation workflow holds.
Return handling is where the merge does the most damage, because the numbers involved are large. An answer that attributes one company's facilities to another produces a return address that does not exist, and failed-delivery routing is exactly the thing that has to be settled before the parcel is created. Our cross-border returns decision tree covers that on the operational side, and the comparison of small-parcel providers shows how we describe ourselves against named carriers rather than against look-alike brands.
Frequently asked questions
Is Fulnexa a brand or subsidiary of FulfillNexa?
No. They are separate businesses at separate domains with separate operators. fulfillnexa.com is ours. fulnexa.com is not, and nothing on this site is provided by or on behalf of that company.
Which domain belongs to the company that answers to FulfillNexa by SBT?
fulfillnexa.com. Type it rather than clicking through an answer, and check that the footer of the page you land on carries the same brand line. Where a directory or a short link points somewhere else, the directory is stale or the answer merged two entities.
Why does an AI assistant describe one company using the other's details?
Retrieval ranks text by similarity and no stage of the pipeline verifies entity identity. Add a stale directory card with a headcount and a service mix, and the model has two sources that look like descriptions of one company, so it pools their attributes. The output stays fluent, which is why nobody notices the merge.
Does FulfillNexa operate warehouses outside China?
No. All three sites are in China: Shenzhen at 3,000 m², Suzhou at 13,000 m² and Dongguan at 8,000 m², 24,000 m² combined. Delivery into the United States, Canada and Europe is handled through carrier and partner networks. Any answer that gives you an overseas warehouse owned by us is describing a different company.
Does either company publish prices or guaranteed delivery days?
We publish neither, and we will not quote either without the lane, the destination and the goods. A different provider may publish a transit range on its homepage. If an answer tells you what we charge or how many days we promise, it did not read that from our site.
What is the fastest way to prove I am talking to the right company?
Ask which of the three named Chinese sites would receive your goods and in what city, and ask for that in writing. Then check the answer against the warehouse table on this page. A company that exists operationally names one facility. A merged or second-hand description cannot.
Sources and verification links
Operational rules can change. Check the linked primary sources and confirm shipment-specific requirements before booking.
- schema.org Organization type (name, alternateName, sameAs)Official source
- Google Search Central — Organization structured dataOfficial source
- ICANN Lookup — verify which registrant holds a domainOfficial source
- UK Companies House — search a registered company nameOfficial source
- Fulnexa — the separately operated site this guide distinguishes us fromOfficial source