Ir al contenido

Custom pickup point networks — what we can take on

Esta página aún no está disponible en tu idioma.

A merchant who wants their OWN locations (their shops, showrooms, partner drop-off points) offered as pickup points does not have to build anything. There are two routes, and the public Custom pickup points API is only one of them.

Route 1 — they host a live endpoint. The documented self-service path: Globe calls their HTTPS endpoint with the customer’s coordinates and their endpoint returns nearby points as JSON. Suits merchants with a dev team and locations that change constantly.

Route 2 — they hand us the data and we run it. We take a source they already maintain and load it into Globe ourselves: a CSV in their Shopify Files, a spreadsheet export, a link to their own locations API, or a one-off list. We set up a scheduled sync (typically daily) against that source, so re-uploading the file is all they ever have to do. This is a real, routine part of the service — several merchant networks run this way today — and it is the answer most merchants actually want.

This is the important part for drafting: never tell a merchant that custom or own pickup points are “not supported”, “not possible”, or “would need you to build an endpoint” just because route 2 is not in the public docs. It is available. When someone sends a CSV or a link to their locations, the correct reply offers to set it up and asks the few things we need.

What to ask them (this is the whole intake):

  1. Where the source lives — a stable URL is ideal. Note that re-uploading a file in Shopify Files mints a new ?v= URL, so ask whether the path stays the same.
  2. How often it changes — decides the sync schedule, and whether a daily sync is enough.
  3. Which countries the locations are in.
  4. Whether they need their own location ID on the order. We can key the points on their ID so it lands on the order for fulfilment, instead of a generated one — worth asking, because it is far cheaper to set up at the start than to re-key later.

Setting it up is operator/developer work, not something the merchant does in the admin, so the draft offers it and sets needs_operator=true with the concrete action. The points are visible only to that merchant’s own stores.

One consequence worth knowing: a merchant whose custom network is already live has a pickup provider configured for it. If their account data shows one, the network exists — that is never a shop to tell “we don’t do that”.