C cenaly.ru
Start free

QuickShipper: OAuth client and a choice of Georgian couriers

Delivery aggregator for Georgia: requesting Delivery API access by email, Client ID and Client secret, a pickup point with coordinates, the sandbox and switching to production

3 min read Admin panel demo
On this page 8

🇬🇪 QuickShipper: OAuth client and a choice of Georgian couriers

QuickShipper is a delivery aggregator for Georgia: its own fleet plus connected local carriers. One card gives the buyer at checkout several courier options, each with its price and time.

Where it is set up: Control panel → “Shipments” → “Delivery services” button (or the location card → WEB → “Delivery services”).

What you need#

  • for the sandbox — the login and password of a test.quickshipper.ge test account (open registration, no keys needed);
  • for production — a Delivery API OAuth client: Client ID and Client secret (issued by the carrier on request, not self-issued in the account);
  • the address, city, coordinates and phone of the point where the courier picks up orders.

Sandbox: the test account#

  1. Register at test.quickshipper.ge.
  2. Connect couriers: Parameters → Integration → Activation of courier services. To try it out, “Add your own delivery type” — an own delivery type with a name and price — is enough; with no couriers connected there are no rates.
  3. Enter that account’s login and password in the carrier card and leave the Client ID empty — QuickShipper’s test Delivery API client is shared and published in their documentation.

Production: keys from the carrier#

  1. Create a business account at qshpr.com.
  2. Email info@qshpr.com: “please grant Delivery API access for an online shop integration”, and include the account email.
  3. The carrier sends a Client ID and Client secret (sometimes also a login and password for login-based access) and reviews the integration.

What to enter in the carrier card#

Field What to enter
Account login and password in the sandbox — of test.quickshipper.ge (that is enough); in production — only if the carrier granted login-based access
Client ID production only: the OAuth client ID from the carrier’s email
Client secret production only: the client secret from the email
Environment “Sandbox” until the carrier’s review, “Production” after it
Sender address and city where the courier picks up parcels
Sender coordinates latitude and longitude of the pickup point, e.g. 41.7151, 44.8271 — QuickShipper prices by distance
Sender name and phone contact for the courier, phone as +995…
Limit providers optional: QuickShipper provider numbers, comma-separated; empty — all connected

Checking#

  1. Click “Save”.
  2. Click “Test connection”: provider rates appear under the card. “Mock mode” means the keys are not connected and the rates are demo.
  3. Tick “Enable QuickShipper”.

Sandbox and production#

  • Without keys the card shows demo rates.
  • “Sandbox” environment — real responses of the QuickShipper test server. Buyers do not see these rates and no waybill is created from an order: nobody delivers a test order.
  • “Production” environment — switch to it once the carrier confirms the integration passed its review. From then on QuickShipper rates appear for buyers at checkout and a waybill can be created from the order card.

Common problems#

  • No reply to the email — write again or call QuickShipper support: API access is granted manually.
  • “Test connection” reports an authorization error — check that the selected environment matches the keys: the test account login does not work in production, and production keys do not work in the sandbox. invalid_grant — Invalid password means a wrong account password.
  • No rates — no courier is connected in the QuickShipper account (“Activation of courier services”), the pickup point has no coordinates, or the buyer’s address is outside the providers’ area.
  • The waybill does not print in the sandbox — the QuickShipper test server’s waybill generator is currently broken; the order is still created.

← All delivery carriers

Was this article helpful?