Prodsyncr onboarding

Step-by-step walkthrough

Shopify setup

Follow these steps to configure your Shopify store from scratch. Each step includes the Action, key UI elements, expected Outcome, and relevant backend tie-ins. Add screenshots where noted.

1) Sign in

Refine: Use your Shopify account (or create one) at https://www.shopify.com/login. If you don’t have a store yet, Shopify will guide you to create one after sign-in.

2) Create app on dev dashboard

What you’re seeing: the Shopify developer area (Partner Dashboard) where you can manage apps.
What to do: navigate to Apps (or My apps) and choose Create app.
Outcome: Shopify creates an app shell and opens the app setup flow.
Screenshot S2 — Shopify Partner / Developer dashboard

3) Fill in the app name

What you’re seeing: the app creation form with a field for the app name.
What to do: enter a clear name (for example “Prodsyncr”) and save/create.
Tip: use a name merchants will recognize in the Shopify Admin when installing the app.
Screenshot S3 — App name & basic details

4) Fill in the app scopes on the Access tab

What you’re seeing: the Access (or API access) area listing permission scopes.
What to do: enable the minimum required scopes for reading products, inventory, and related resources.
Scopes needed: read_product_feeds,read_product_listings,read_products,write_products,unauthenticated_write_bulk_operations,unauthenticated_read_bulk_operations
Outcome: the app will be allowed to request tokens with those permissions during installation.
Screenshot S4 — API access scopes (Access tab)

5) Overview app versioning

What you’re seeing: an overview of the app’s versions or releases.
What to do: confirm you’re working on the correct version (for example, the latest development version).
Outcome: changes you make (scopes/settings) apply to the intended version.
Screenshot S5 — App versions / releases

6) Overview app credentials

What you’re seeing: the app credentials (API key, client ID/secret, and other identifiers depending on app type).
What to do: copy the credentials you need into your secure secret store or Prodsyncr configuration.
Security note: never paste credentials into tickets or shared docs; rotate them if they were exposed.
Screenshot S6 — API keys / client credentials

7) Install app on dev dashboard

What you’re seeing: the option to install or test the app from the developer dashboard.
What to do: choose Install app (or Test on development store) and select the correct development store.
Outcome: Shopify starts the installation flow and asks you to approve the requested scopes.
Screenshot S7 — Install / test the app (developer dashboard)

7) Install app on shopify

What you’re seeing: the Shopify Admin installation/authorization screen showing the requested permissions.
What to do: review the permissions and click Install (or Approve) to complete the install.
Outcome: the app becomes available in the store’s Apps list, and Shopify issues the access token according to the selected auth model.
Screenshot S8 — Approve app install in Shopify Admin

Prodsyncr

1) Sign in

Action: Enter credentials and sign in. Outcome: You are redirected to the Dashboard.

UI: Enter Email address and Password; optionally tick Remember me; click Sign in.
Outcome: Redirected to Dashboard upon success.
Backend: Session is created after authentication.
Screenshot 1 — Sign in screen
What you’re seeing: the login form with Email address, Password, and the optional Remember me checkbox.
What to do: enter your credentials and click Sign in.
Outcome: on successful authentication a session is created and you are redirected to the Dashboard, giving you secure access to connections, imports, and sync jobs.

2) Dashboard overview

Action: Review high-level metrics: Marketplaces, Platform Products, Sync Activity, Success Rate, and Recent Sync Activity.
Screenshot 2 — Dashboard

What you’re seeing: the Dashboard with high-level metrics such as Marketplaces, Platform Products, Sync Activity, Success Rate, and Recent Sync Activity.
What to do: use this page as a quick health check before you continue with imports or syncs. Look for failed jobs or a suspiciously low number of imports.
Tip: Use this to spot failures or zero-import scenarios before proceeding.

3) Connections

Action: Create connections for Shopify and bol via “New connection” and provide required credentials. Enable the connection.
Screenshot 3 — Connections list (empty state)

What you’re seeing: the Connections page before any connections have been created.
What to do: click New connection to add both a Shopify connection and a bol connection, fill in the required credentials, and enable each connection.
— Connection details page
For shopify

For bol.com

Bol.com credentials

Outcome: once saved, the list will show the connections as Active with metadata such as the Shopify shop domain or bol retailer ID.
Backend tie-in: the app validates the provided API credentials, stores tokens/secrets securely, and marks the connection as Active when validation succeeds.
Backend: Validates API credentials; securely stores tokens/secrets; marks connection Active.
Outcome: Connection list shows Shopify and bol as Active with metadata (e.g., shop domain, retailer ID).

4) Product Imports

Screenshot 4 — Product Imports page

What you’re seeing: the Product Imports overview, listing import jobs and their progress.
Note: After you create and enable a Shopify connection, product imports typically run automatically in the background. Manual imports are usually not necessary.
When to use manual import: primarily for troubleshooting (e.g., to verify credentials/scopes) or to force a refresh if you suspect data is stale.

Action: Normally no action required—imports start automatically after you create and enable a Shopify connection. Use “Import from Shopify” only to troubleshoot (e.g., to verify credentials/scopes) or to force a manual refresh.
Screenshot 5 — Import from Shopify dialog

What you’re seeing: the dialog that appears when you choose Import from Shopify.
What to do: select the Shopify connection you want to import from and confirm to start the import job.
Reminder: imports may require two runs—the first to fetch products into an internal queue, and the second to ingest and normalize them into Platform Products.
Backend: Queues an import job; fetches products from Shopify; normalizes into platform product schema.
UI: Toast indicates import started; Product Imports page shows job progressing from CREATED to COMPLETED with 100% progress.

Important: imports may require two runs

First run (fetch phase): the app starts a background fetch that pulls products from the connection into an internal queue. Depending on store size, this can take a while.
Second run (ingest phase): once the fetch has finished and items are in the queue, run the import again to actually ingest/normalize queued products into Platform Products.
If Platform Products is still empty, wait a bit, refresh, and re-run the import.

5) Platform Products

Action: Review imported products. Columns include media, EAN, SKU/Barcode, title, identifiers, price & stock, source, and sync status.

Backend: Reads normalized product catalog; shows if any previous syncs exist (e.g., “No Syncs”).
Screenshot 6 — Platform Products overview

What you’re seeing: the Platform Products table populated with your normalized product catalog.
What to check: verify key columns such as media, EAN, SKU/Barcode, title, identifiers, price, stock, source, and current sync status (for example “No Syncs” when nothing has been synced yet).
Troubleshooting tie-in: if this view remains empty after running an import, follow the guidance above about the two-phase import (wait for the fetch phase to complete and then run the import again to ingest into Platform Products).

Screenshot 7 — Platform Products details

What you’re seeing: a closer look at an individual platform product’s data (identifiers, price/stock, and source information).
What to do: confirm that the data coming from Shopify is correct before you sync to bol.
Why it matters: any incorrect identifiers, price, or stock values here will propagate to bol during synchronization.

6) Select products → Sync to marketplace

Action: Multi-select products and choose “Sync to Marketplace”. Pick target Marketplace (bol) and the target connection; submit.

Backend: Creates marketplace-product drafts for bol; initializes attribute set with defaults/derivations from Shopify data.
Screenshot 8 — Select products and open Sync to Marketplace
What you’re seeing: multiple products selected in Platform Products with the bulk action menu visible.
What to do: select the products you want to publish and choose Sync to Marketplace from the bulk actions.
Backend tie-in: this will trigger creation of marketplace-product drafts for these selections.

Screenshot 9 — Choose marketplace and connection

What you’re seeing: the dialog to choose the target Marketplace (bol) and the specific bol connection.
What to do: pick bol as the marketplace and select the correct bol connection, then confirm to create the drafts.
Backend tie-in: this initializes marketplace-specific attribute sets based on the Shopify source data.

7) Edit attributes (per-product)

Action: In the edit page, refine marketplace-specific fields: title, description, category, attributes, pricing, stock, and shipping. Warnings appear when required fields (e.g., category) are missing or stock is zero.

AI Autofill: Use the AI button to prefill titles, descriptions, and attributes derived from the product’s data and marketplace catalog rules. Review before saving.
Backend: Validates required attributes for bol; prepares payload for offer/content upsert.
Screenshot 10 — Marketplace product edit screen

What you’re seeing: the bol-specific edit page for a single marketplace product.
What to do: adjust title, description, price, stock, and shipping to meet bol’s requirements.
Backend tie-in: edits here determine the payload that will be sent to bol during sync.

Screenshot 11 — Required fields and category selection

What you’re seeing: required fields (such as category) and other mandatory attributes that must be completed.
What to do: pick a valid category and fill all required fields to clear validation errors.
Why it matters: missing required attributes will block successful synchronization to bol.

Screenshot 12 — Validation warnings and stock issues

What you’re seeing: warnings for problems such as missing attributes or zero stock.
What to do: resolve each warning—update stock, fill in missing fields, or adjust configuration until warnings disappear.
Troubleshooting tie-in: this is your first place to fix issues before they turn into sync failures.

Screenshot 13 — AI Autofill suggestions

What you’re seeing: AI Autofill proposing marketplace-ready titles, descriptions, and attributes.
What to do: review and edit AI suggestions where needed, then accept and save.
Backend/AI tie-in: suggestions are generated from Shopify product data and marketplace heuristics, but operators must always confirm them before syncing.

8) Start synchronization

Action: Click “Start Synchronization”. A toast confirms the sync started.

Backend: Enqueues a sync job; posts offers/content to bol APIs; tracks job state transitions (Pending → In Progress → Succeeded/Failed).
Screenshot 14 — Start Synchronization action

What you’re seeing: the Start Synchronization control for the edited bol products.
What to do: click Start Synchronization to send the prepared offers/content to bol.
What happens next: a toast confirms the sync has started and a sync job is enqueued and tracked through its lifecycle.

9) Sync history and monitoring

Action: Open Sync History to see all jobs with type, status, item counts, AI confidence (if applicable), start time, and duration. The Dashboard updates aggregated metrics accordingly.

Backend: Persisted job logs and metrics enable auditing and troubleshooting.
Screenshot 15 — Sync History overview
What you’re seeing: the Sync History list of jobs with type, status, item counts, start time, and duration.
What to do: use this list to monitor overall sync health and quickly spot failed or long-running jobs.
Dashboard tie-in: results shown here roll up into the aggregate metrics on the Dashboard.

Screenshot 16 — Sync job details and troubleshooting

What you’re seeing: details for a single sync job, including per-item results, errors, and (where available) AI confidence metrics.
What to do: open failed jobs, inspect error messages, fix the underlying issues (attributes, identifiers, stock, credentials), and re-run synchronization.
Why it matters: this is your main audit and troubleshooting view when merchants report missing or incorrect offers on bol.