intelligent.pageDocs

Ship-Mojo

ShipMojo could not be identified as a live product; the evidence points to a misspelling of Shipmozo, the Indian shipping aggregator.

ShipMojo could not be identified as a live shipping product anywhere. Every domain that would plausibly carry it either does not resolve or is parked, and the only artefact on the open web that uses the name is a WooCommerce plugin repository titled "Shipmojo-for-woocommerce" whose entire contents, code and documentation, are about Shipmozo, the Indian multi-carrier shipping aggregator operated by Tensor Logistics Private Limited. The most likely explanation is a transcription error: a "z" read as a "j". This page records the checks so the catalogue entry can be corrected rather than left to rot, and points at the page that actually covers the product: /connectors/shipmozo.

Warning

Recommendation: retire this catalogue entry and merge it into Shipmozo, or correct the spelling. Do not scope a connector from it. If a customer or a data source genuinely says "ShipMojo", ask them to confirm the domain before anyone writes code.

At a glance

What it is

Nothing, as far as can be established. The checks:

Domains. shipmojo.in resolves and returns HTTP 200, but the response is a two-line HTML document that redirects to /lander, and /lander is a GoDaddy parking page carrying window.LANDER_SYSTEM="PW" and the GoDaddy parking asset bundle from img1.wsimg.com/parking-lander. It is a parked domain with no content. The site's own sitemap contains exactly one URL, https://shipmojo.in/lander, which is the parking page.

Every other candidate fails to resolve in DNS: shipmojo.com, shipmojo.co, shipmojo.co.in, shipmojo.io, shipmojo.net, shipmojo.app, shipmojo.ai, shipmojo.org, shipmojo.shop, shipmojo.tech, shipmojo.xyz, shipmojo.us and getshipmojo.com.

History. The Internet Archive's most recent capture of shipmojo.in, dated 14 August 2024, is the same redirect-to-lander document. So the domain has been parked for at least two years, and there is no archived version of a working product.

App stores. apps.shopify.com/shipmojo and apps.shopify.com/ship-mojo both return 404.

Aggregator directories. ClickPost publishes carrier integration pages for 428 carriers; enumerating its sitemap returns no ShipMojo page. Unicommerce's public integration list, which names more than a hundred logistics partners, does not contain the string.

Code. The GitHub repository index returns two repositories matching "shipmojo". One is an empty personal repository. The other, chiranjitWeb/Shipmojo-for-woocommerce, is the informative one: despite the repository name, its README is titled "Shipmozo for WooCommerce, Plugin" and describes "A custom WooCommerce plugin that integrates Shipmozo shipping API". Every file inside is named shipmozo-*, every class is Shipmozo_*, the configuration screen is "WooCommerce, Shipmozo", and the API base URL it calls is Shipmozo's. The repository name is simply misspelled.

That is the whole evidential basis for the identification. It is circumstantial but consistent: a parked domain, no product anywhere, and exactly one artefact bearing the name, which turns out to be about Shipmozo.

If the intended platform is Shipmozo

Shipmozo is a real Indian multi-carrier shipping aggregator run by Tensor Logistics Private Limited of Gurugram, with roughly 27 courier partners, coverage of more than 29,000 pin codes, D+1 or D+2 cash on delivery remittance and no platform fee. It has a working REST API at https://shipping-api.com/app/api/v1 authenticated with a public-key and private-key header pair, though it publishes no developer documentation. All of that is covered at /connectors/shipmozo.

Other things that might be meant

If Shipmozo is not the intended platform, the next most likely candidates, in rough order:

  • Shipmonk, a United States third-party logistics and fulfilment provider. Phonetically close, entirely different business, real API.
  • Shipway, an Indian shipping and returns platform. Different name, similar segment.
  • A private or white-label brand with no public web presence, which the customer would have to name directly.

None of these was investigated for this page, because none of them is what the catalogue said.

API access

Not applicable. There is no product and therefore no access path, no credentials, no approval process and no cost.

Authentication

Not applicable. Nothing exists to authenticate against.

Objects we can read

Nothing. There is no platform, so there are no orders, order items, products, listings, inventory, shipments, returns, payments, customers or locations to read.

Writing back: listings, price and stock

Not applicable, and doubly so. There is no product; and if the intended platform is Shipmozo, that is a carrier aggregator which owns no listing, price or stock either, so the answer would still be not applicable. On Shipmozo the write path is shipment creation and cancellation, documented at /connectors/shipmozo.

Webhooks and notifications

Not applicable. Nothing to subscribe to, nothing to poll.

Rate limits and pagination

Not applicable.

Mapping to the unified model

Nothing maps. No row should be written to orders, order_items, listings, inventory, shipments, returns, settlements, customers or locations from this entry. If a pipeline is already keyed on a channel value of shipmojo or ship-mojo, redirect it to shipmozo and reconcile, rather than leaving two channel identifiers for one platform.

Gaps and open questions

  • Where did the name come from? If the catalogue entry originated from a customer list, a scraped directory or a partner spreadsheet, tracing the source would settle whether this is a typo for Shipmozo or a genuinely obscure private brand. That is the one useful next step.
  • The Shipmozo identification is inference, not proof. It rests on a single misspelled repository name. Strong, but a customer confirmation would close it.
  • Non-web presence. A shipping brand can operate entirely through an account manager and a login-walled panel with no marketing site, particularly a regional or franchise operation. That possibility cannot be excluded from web evidence alone, but a parked domain and zero aggregator listings make it unlikely.
  • Web search was unavailable for this research pass, so the checks were direct: DNS, HTTP, sitemaps, archive captures, app stores, aggregator directories and the GitHub repository index. A search engine pass might surface a regional brand that none of those cover.

Sources