Skip to main content
  1. Sandbox done. GO JOE’s portal ticks off a go-live check from your sandbox traffic and can send you a signed test webhook (ping). Your ERP handles, against the sandbox:
    • a webhook with a valid signature (and rejects a tampered one),
    • fetching the order and downloading the prescription,
    • accept with your order number, packed, and either out_for_delivery + completed (own shipping) or ready_for_pickup + completed (pick-up),
    • order.prescription_signed (download again),
    • the same webhook twice (no duplicate ERP order),
    • catching up via GET /events after your endpoint was down,
    • a full stock push of your catalogue and PATCH updates for single articles.
  2. Products. GO JOE maps your article numbers (pharmacy_sku) to the GO JOE catalogue, from the SKUs your sandbox pushes reported as unmapped.
  3. Live key. GO JOE issues a gj_live_… key and you set the production webhook URL. Each pharmacy confirms your account may act for it.
  4. First weeks. The pharmacy keeps getting the usual order e-mail as a safety net while the integration proves itself.
  5. Afterwards. GO JOE watches webhook failures and orders that are not accepted in time, and contacts your technical contact if something looks off.