Sync Hive Pledge Manager with Shopline

Start by adding the Hive Pledge Manager app to your Shopline store. You authorize Hive's existing app rather than creating your own custom app or entering app credentials.

1. Install or open Hive Pledge Manager in Shopline and follow the authorization prompts.
2. Sign in to Hive when prompted and select the creator company that owns the projects you want to fulfill.
3. In Hive, open Account Information > Advanced > Shopline Integration > Shopline Setup.
4. Confirm the Shopline store domain, click Connect Shopline, and complete the authorization.
5. Return to Shopline Setup and confirm that the connection is Verified.

You need permission to install apps in Shopline and manage the selected company in Hive. If the app is not available to your store, contact Hive support for installation access.

Automatically send newly Verified backers assigned to the Shopline fulfillment destination controls automatic export when a backer moves from Open to Verified. Assign the intended backers or fulfillment segments to Shopline before using this setting. Switching it on does not automatically send every backer who was already Verified.

Leave automatic sending off while preparing your mappings or running your first test. You can still send individual Verified backers manually.

Mark exported Shopline orders as paid creates newly exported orders with an imported external payment based on the funds recorded in Hive and Kickstarter. Turning it off creates unpaid orders. This does not charge the backer again or transfer money through Shopline.

Disabling automatic sending preserves the store connection, SKU mappings, existing order links, and shipment-update processing.

A webhook is Shopline's notification to Hive that an order or shipment has changed. Hive registers the required order, fulfillment, and app-installation notifications during connection verification.

If your store was connected previously, open Shopline Setup and click Verify Connection & Register Webhooks. You do not need to disconnect or reinstall the app. Hive reuses matching subscriptions and registers any that are missing. If registration fails, the page shows an error.

Disconnecting removes this company's local Shopline mappings, queued exports, order synchronization links, and webhook records. Products and orders already created in Shopline are not deleted.

Uninstall the Hive Pledge Manager app in Shopline as well to revoke its authorization there. Use disconnect when ending or changing the integration, rather than as a way to retry an order.

Open your SKU List. With Shopline connected and verified, use Import / Auto-match Shopline Products to read the store's products and variants and compare them with your Hive catalog.

Hive attempts to match variants using the exact SKU code and stores the Shopline identifiers needed for later exports. Review the Shopline mapping status beside each SKU before sending orders.

Status labels include Mapped, Hive Only, Shopline Only, Duplicate Shopline SKU, Unmapped, and Error.

Use Resolve Shopline SKU Mapping to review unmatched products and conflicts. A blank SKU code or several Shopline variants sharing the same code prevents a safe automatic match. Correct the catalog or choose the appropriate variant through manual mapping.

When a product exists only in Shopline, you can import the selected variant into Hive and map the new Hive SKU to it. Review the project selection before importing.

Before your first export, confirm that all pledge items, add-ons, and freebies that produce shipping SKUs are mapped. Hive blocks an order with missing mappings rather than exporting an incomplete pledge.

For products that exist only in Hive, select the appropriate Hive Only entries and upload them to Shopline. Hive creates unpublished products using the available SKU information, including the SKU code, name, description, image, and MSRP.

Hive saves the resulting product and variant identifiers as the mapping. Review the products in Shopline before publishing them for normal store sales; exporting a fulfillment product does not mean it should automatically become a storefront listing.

The backer must be Verified, the company's Shopline connection must be active, and every included SKU must have a mapping. Hive also validates the address, contact details, and order amounts.

The Hive project's currency must match the Shopline store's currency. Automatic currency conversion is not supported.

For shipment updates to return to the backer, the backer must be assigned to the Shopline fulfillment destination. A successful manual send assigns that destination to the Verified backer.

From the project's Backers tab, choose Send to Shopline for a Verified backer. Hive validates the pledge and shows any missing mappings or other errors before sending. Individual sends and Backer Operations sends run immediately.

For automatic sends, enable the company preference in Shopline Setup. When a backer moves from Open to Verified and is routed to Shopline, Hive queues the export for background processing. Fulfillment-segment sends also use the queue.

Automatic sending requires Hive's scheduled Shopline processing to be enabled and running. If a queued export remains pending, contact Hive support rather than repeatedly resending it.

Shopify and Shopline have separate connections and send actions. Check your settings carefully if both are enabled, as the same backer can be exported to both platforms.

A crowdfunding bundle's collected price may differ from the retail prices of its individual SKUs. Hive calculates the merchandise value as funds recorded from Kickstarter and Hive payments, less shipping and collected taxes, then allocates that value across the mapped items using SKU MSRP as a weighting value.

Shipping and collected tax are included in the export so the order total remains aligned with Hive. Currency rounding can produce split lines for the same variant; check the combined quantity and total.

Order creation bypasses inventory deduction and requests that Shopline suppress order and fulfillment receipt emails for the import. Review your own fulfillment notifications separately before shipping.

While the backer remains Verified, use Send to Shopline again if you need to retry or send supported contact and shipping changes. Hive keeps a durable link to the original Shopline order.

• If the exported information has not changed, Hive reports that no changes are needed.
• If supported contact or shipping details changed, Hive updates the linked order.
• If products, totals, or paid status changed, Hive stops for manual review rather than replacing financial or item information automatically.
• If the linked order is missing or cancelled, Hive blocks the resend for review.

Archiving an order does not reset its Hive link. There is no automatic replacement-order action. If a creation attempt has an uncertain outcome, inspect Shopline and contact Hive support; do not disconnect the integration to force another order.

Hive marks a backer Shipped only when the remote order is fully shipped or fulfilled and has a tracking number. Partial shipments and cancelled orders do not trigger that transition. A shipped order without tracking is not enough.

The connection must remain active, the order must be linked to the correct company's backer, and that backer must be assigned to Shopline fulfillment. Hive applies tracking to backers that are Verified or already Shipped.

If Shopline returns several tracking numbers or carriers, Hive combines them in its existing tracking fields and uses the first available tracking URL. Tracking details that exceed the field limits require manual review.

When an order or fulfillment changes, Shopline sends a signed notification to Hive. Hive checks its authenticity and stores the event. The background worker then retrieves the current Shopline order, finds its linked backer, and saves the shipment status and tracking information.

This means a webhook can be received successfully while the backer is still waiting for an update. Allow time for the next processing run. Hive's recommended worker schedule is every five minutes.

If events are received but remain pending, Hive support should check the scheduled worker. Receiving notifications alone does not process them.

When enabled, Hive's background reconciliation checks linked Shopline orders and retrieves shipment details even when a webhook was missed. It cycles through known order links, including older orders.

An order fulfilled before webhook registration does not need to be exported again. Reconciliation can recover its current shipment details. Contact Hive support if the order remains unsynchronized, since reconciliation must be enabled and running.

For administrators, received webhooks are processed by the Shopline worker even when queued exports and reconciliation are disabled. Those background features have separate enablement requirements.

Importing Shopline tracking does not automatically send a shipment confirmation email from Hive. Choose your normal Shopline notification workflow or send a deliberate communication through Hive, keeping duplicate messages in mind.

For the separate CSV tracking workflow, see Import tracking numbers, carriers and tracking URLs.

1. Connect: install Hive Pledge Manager, authorize the correct company and store, and verify the connection. For an existing connection, use Verify Connection & Register Webhooks. Expect a success message confirming registration.
2. Map: import Shopline products and match a test SKU. Check that the correct variant is marked Mapped. An unmapped item should block export and identify the missing mapping.
3. Send: send one Verified test backer. Confirm the HIVE order reference, address, item quantities, currency, shipping, tax, and total in Shopline. Check paid or unpaid status against your chosen setting.
4. Retry: send that unchanged Verified backer again. Expect the original Shopline order to remain linked, with no duplicate. If testing address updates, change a controlled test address in Hive and verify that the existing order is updated.
5. Fulfill: fully fulfill the linked test order with tracking. After background processing, expect the same Hive backer to show Shipped and the returned tracking details.
6. Check partial shipment behavior: on a separate suitable test order, fulfill only part of the items. Expect Hive to wait for full fulfillment with tracking before marking the backer Shipped.
7. Check automatic sending if needed: enable the preference, route a separate test backer to Shopline, and move that backer from Open to Verified. Confirm that background processing exports one linked order.

Use separate test backers for cases that change an order's lifecycle. Cancelling, copying, or archiving a production order is not required to test webhook delivery.

If the order was fulfilled before notifications were registered, first verify the webhook setup. If Shopline offers an edit action for that fulfillment and you have a genuine tracking correction to make, saving it can generate a new fulfillment update. Available controls depend on Shopline's order state and your permissions; do not assume that every shipped order can be edited.

If editing is unavailable, use a separate linked test order for a fresh fulfillment event, or ask Hive support to check reconciliation for the existing order. An order created manually in Shopline without a Hive link can generate notifications, but cannot update a Hive backer.

When reporting an issue, include the Hive backer ID, Shopline order reference, approximate time of the change, and the expected result. Hive administrators can check whether a notification arrived, whether it is pending or failed, and whether the worker applied it. Do not include access tokens or app secrets.