Web Store

BigCommerce

< Back to All Connectors
Connect your AI to BigCommerce
Ecommerce managers, merchandisers, and customer support teams run the store through BigCommerce, but orders, products, customers, and coupons live on separate screens that take time to export and reconcile. AI can answer those questions in seconds, but only if it stays read-only, so it cannot change store data, and shares customer details and order contents only with people entitled to see them.

‍

Start a Trial
Get a Live Demo

Why it matters

Capabilities that matter most for BigCommerce

01

Read live store data from any AI client

Ask about orders, products, variants, customers, coupons, categories, and gift certificates and get answers from the store as it is now, not from last week's export.
02

Tools and prompts ready in the app store

17 read tools and 15 read-only prompts for jobs like order reviews and catalog pricing audits are ready to add to your account in a click.
03

Read-only by design

The tools only read. Nothing in the store can be changed through them, and customer details and order contents are shared only with people who are allowed to see them.
03

One question across BigCommerce and your other systems

Cross-system prompts line up BigCommerce with the CRM, ERP, accounting, and email platforms you already run, so a question that spans both has one answer.

Use cases

Example AI Use Cases for BigCommerce

Filters

scenario

-

Spot-checking prices by eye across a long catalog means a negative margin, a zero price or a sale price above the regular price can sit unnoticed among thousands of rows. Variants can carry their own prices too, so a product that looks fine can still hide a bad variant.

What popdock provides

--

Optionally name a brand or a minimum price, and it reads the BigCommerce products and applies fixed pricing rules: zero or empty price, sale price above price, cost above the selling price, retail price below price, and margin under 10 percent. For flagged products it also checks up to 20 products for variants with the same problem. Results are sorted by severity and show the figures behind each flag. It only reads and recommends, never edits a price, and says so plainly when nothing is found or when results may be truncated.

Business outcome

---

Pricing problems surface in severity order with the figures behind each flag, so negative margins are caught by a check rather than by eye.
See Full Use Case

scenario

-

Promo codes get created for a campaign and then forgotten, so expired codes stay enabled and generous ones keep working. The team usually finds out only when a customer uses one, because nobody lists the enabled coupons and checks each against its dates and usage.

What popdock provides

--

Optionally give a number of days ahead to watch, and it reads every enabled BigCommerce coupon and sorts them into expired but still enabled, expiring soon, never used, exhausted and risky. Risky means a percentage of 50 or more, or a large amount with no minimum purchase. You get one table per class and the ids of expired coupons someone could disable. It only reads, and disabling is left to a separate job that asks you first. It stops and says so when there are no enabled coupons or results may be truncated.

Business outcome

---

Stale and risky promo codes are listed by class before a customer finds them, with disabling left for you to decide.
See Full Use Case

scenario

-

Finding out what one customer bought and how Drip treats them means opening BigCommerce for the orders, then Drip for the subscriber, and matching the two by email. It is easy to miss that a buyer is unsubscribed or sits in no campaign.

What popdock provides

--

Give a customer email and optionally how many days of orders to review, and it finds the customer in BigCommerce, totals their orders and spend, then looks the same email up in Drip. It shows Drip status, tags, lead score, lifetime value and campaigns next to the orders, and flags a non-active status, spend with no campaigns and lifetime values that differ widely. It only reads on both systems, stops if several BigCommerce customers match, and reports absence from Drip rather than guessing.

Business outcome

---

One customer's orders and Drip standing appear in one view, so an unsubscribed buyer is spotted before the next campaign.
See Full Use Case

scenario

-

Checking what an online customer has ordered against what they owe means logging into BigCommerce and then Dynamics GP. The two systems share no customer id, so someone has to guess which GP customer is the same company as the store customer.

What popdock provides

--

Give a customer email and optionally a lookback in days, and it totals the customer's BigCommerce orders, refunds and unpaid orders. It then searches Dynamics GP by company or name, prefers the match whose email agrees, and shows balance, credit limit, hold flag and open receivable documents. If several GP customers match it asks you to choose, and it says when a match was by name only. It only reads on both systems and stops when a record is missing on either side.

Business outcome

---

Order activity and receivables sit side by side, with name matches labelled as such, so credit and collection questions rest on the right account.
See Full Use Case

scenario

-

Support staff jump between BigCommerce for orders and HubSpot for the contact, deals and tickets, and the pieces rarely line up. Context gets missed, such as an open ticket or a refunded order, because nobody has the whole customer on one screen.

What popdock provides

--

Give a customer email and optionally how many recent orders to show, and it reads the customer and latest orders from BigCommerce, then finds the HubSpot contact by the same email and reads their deals and tickets. The report covers identity, orders, deals, tickets and anything inconsistent. It only reads, says which side is missing when the customer is absent from one system, and shows both values when names or companies disagree.

Business outcome

---

Support sees orders, deals and tickets for one customer together, with disagreements shown rather than hidden.
See Full Use Case

scenario

-

A support or account rep opens BigCommerce for the orders and Pipedrive for the relationship. Refunds in one system and open deals in the other are easy to miss, and a name that looks similar can send them to the wrong person.

What popdock provides

--

Give a customer email and optionally a lookback in days, and it finds the customer in BigCommerce, totals orders, spend and refunds, then finds the person in Pipedrive by email. It adds the organization, deals with status, value and stage, and recent activities, and ends by saying whether the CRM view and the store view agree. It only reads on both systems and lists the matches and stops if several BigCommerce customers match.

Business outcome

---

Reps walk into a conversation knowing the orders, refunds, open deals and last contact, with no guessing about who is who.
See Full Use Case

scenario

-

Customers who place large orders can quietly drop out of your email program, because nobody checks whether they are being emailed. Finding them means pulling big orders from BigCommerce and then looking up each address and its recent sends in Constant Contact.

What popdock provides

--

Give a minimum order total, and optionally a start date and a quiet period in days, and it reads the large BigCommerce orders and confirms each customer email. It checks each address in Constant Contact for a contact and for campaign sends in the quiet period, then groups customers as not in Constant Contact, in Constant Contact with no recent send, or recently emailed. Guest orders are listed separately, and contacts without send permission are flagged as not emailable. It only reads on both systems.

Business outcome

---

Big spenders who are not being emailed are named with order totals, so the gap can be closed by a person who decides what to send.
See Full Use Case

scenario

-

Brand managers add up a brand's products, stock and sales across several screens, copying figures into a sheet. A hidden product or a similar brand name can skew the total, and out-of-stock items that are still visible are easy to overlook.

What popdock provides

--

Name a brand and it finds the matching BigCommerce brand, trying a partial match if the exact name fails, and stops to list the options if more than one matches. It then reads the brand's products and reports the count, visible versus hidden, featured products, price range and average, total stock and units sold, the five products with the most units sold, and visible products that are out of stock. It only reads and says so if nothing is found or results may be incomplete.

Business outcome

---

A brand's catalog position is summarised in one answer, with ambiguous brand names resolved before any figures are added up.
See Full Use Case

scenario

-

A support or account rep opens BigCommerce for the orders and Nutshell for the relationship. Refunds in one system and open leads in the other are easy to miss, and matching a store customer to a Nutshell contact by name alone invites mistakes.

What popdock provides

--

Give a customer email and optionally a lookback in days, and it finds the customer in BigCommerce and totals orders, spend and refunds. It then finds the Nutshell contact by name, keeps only the one whose emails include the address, and reads the account, leads with status, value and expected close, and recent activities if needed. It ends by saying whether the CRM and store views agree. It only reads on both systems and stops if several customers match.

Business outcome

---

Reps see orders, refunds and open Nutshell leads in one brief, with the contact confirmed by email rather than by name.
See Full Use Case

scenario

-

Answering one question about a buyer means clicking between the customer, order and line-item screens in BigCommerce. Guest orders carry no customer id, so they are easy to miss, and similar email addresses can lead to the wrong buyer.

What popdock provides

--

Give a customer email and optionally how many recent orders to expand, and it finds the customer in BigCommerce, trying a partial email match if needed, and stops to list the options if more than one matches. It reads their orders, falls back to the billing email for guest orders, and reads the line items for the latest ones. The summary gives lifetime orders, spend and refunds, then each order with status, payment status and items. It only reads and shares only the personal details the question needs.

Business outcome

---

One summary answers a buyer question, with guest orders included and the right customer confirmed before anything is shown.
See Full Use Case

scenario

-

A support agent answering a billing question checks order history in the storefront and the account balance in the ERP separately. Payment status in the store and the remaining amount in the ERP can tell different stories, and it is easy to infer one from the other.

What popdock provides

--

Give a customer email, and optionally a lookback in days and a Business Central company, and it finds the customer in BigCommerce and reads recent orders. It then finds the Business Central customer by email, reads balance, balance due, credit limit and open posted sales invoices, and links invoices to orders where the numbers match. It keeps store payment status and ERP remaining amounts separate, flags balances over the credit limit, and stops if matches are missing or ambiguous. It only reads.

Business outcome

---

Billing questions are answered from both systems at once, with payment status and ERP amounts kept apart instead of guessed from each other.
See Full Use Case

scenario

-

Checking whether a buyer actually opens your email means searching BigCommerce for the orders and Mailchimp for the audience record, then matching by hand. Unsubscribed buyers, or buyers who never open anything, slip through unnoticed.

What popdock provides

--

Give a customer email and optionally a lookback in days, and it finds the customer in BigCommerce and totals orders and spend. It then finds the same email in Mailchimp, lists each audience with status, VIP flag, rating, open and click rates and tags, counts campaign activity in the window, and reports orders attributed to a campaign. It flags unsubscribed buyers who still order. It only reads on both systems, matches on email ignoring case, and says so if a side is missing or partial.

Business outcome

---

Purchases and email engagement for one buyer are read together, so unsubscribed or unengaged customers are spotted quickly.
See Full Use Case

scenario

-

Someone checks a customer in BigCommerce, then searches Constant Contact by hand for their engagement. If the email differs slightly between the two systems, the contact is missed and the customer looks unengaged when they are not.

What popdock provides

--

Give a customer email and optionally a lookback in days, and it finds the customer in BigCommerce and totals orders and spend. It then finds the contact in Constant Contact by email, reads send permission, list membership and activity counts by type, and ends with whether engagement and buying line up. If the email lookup fails it tries the last name and flags any match as unconfirmed. It only reads on both systems and stops if several customers match.

Business outcome

---

Buying and email engagement for one customer are read together, with uncertain contact matches flagged instead of trusted.
See Full Use Case

scenario

-

New store customers are compared to the mailing list by hand, so many never get added. Matching depends on spotting email addresses that differ only by case or trailing spaces, and customers without send permission look the same as those who are subscribed.

What popdock provides

--

Optionally give a start date and a maximum number of customers, and it reads recent BigCommerce customers and checks each email in Constant Contact. You get one table of customers with no Constant Contact contact and a second of contacts whose permission to send is not granted, then counts for checked, missing, present and not permitted. Blank emails are skipped and listed separately, matching ignores case and spaces, and it only reads on both systems.

Business outcome

---

Missing and non-permitted customers are listed with counts, so the mailing list can be fixed by someone who decides who to add.
See Full Use Case

scenario

-

Finance totals gift certificate balances from exports for the accounts, and expiry dates are easy to miss in a long list. Certificates past expiry that still carry a balance raise questions that nobody sees until the audit.

What popdock provides

--

Optionally give a number of days ahead, and it reads every BigCommerce gift certificate with a balance and totals the outstanding amount by status. It lists certificates expiring within the window, certificates past expiry that still carry a balance, and the 10 with the highest balances. It reports only the values on the records and notes that the currency is not held on them. It only reads and says so if nothing is found or results may be truncated.

Business outcome

---

The outstanding gift certificate figure and expiring balances are ready for the accounts without a manual export.
See Full Use Case

scenario

-

Buyers sort the inventory export by stock, then look up each product to see whether it really sells. Low stock on a slow product is not urgent, while a fast seller at zero that can still be bought is, and the export alone does not show the difference.

What popdock provides

--

Optionally give a stock threshold and a brand, and it finds BigCommerce variants at or below the threshold, adding product context for up to 25 products: name, visibility, availability and units sold. It ranks by units sold, then lowest stock, shows warning level and whether purchasing is disabled, and marks zero-stock variants that can still be purchased as urgent. Hidden products are skipped by default. It only reads, flags rather than changes anything, and stops if the brand does not match exactly one.

Business outcome

---

Buyers get a reorder order based on sales as well as stock, with purchasable zero-stock items marked urgent.
See Full Use Case

scenario

-

Marketing exports new sign-ups and cross-checks each one against orders by hand to see who converted. The export also carries more personal detail than the review needs, and the customer group names can be mistyped or ambiguous.

What popdock provides

--

Optionally give a lookback in days and a customer group, and it resolves the group by exact name first, listing candidates and stopping if it is not exactly one. It reads customers created in the window, checks orders for up to 30 of them, and reports new customers per group, the share who have ordered, and the ones with no order yet. Only business contact fields are shown. It only reads and says so if nothing is found or results may be incomplete.

Business outcome

---

Marketing sees who converted and who has not ordered yet, without a manual export or extra personal data.
See Full Use Case

scenario

-

Before a call, an agent opens the BigCommerce admin to see what a customer bought and Salesforce to see what is still open. Adding order totals across currencies gives a wrong number, and the Salesforce contact may not be tied to an account.

What popdock provides

--

Give a customer email and optionally a lookback in days, and it finds the customer in BigCommerce, stopping if none or several match, and reads their orders. It then finds the Salesforce contact by email and reads open opportunities and open cases for the account. The summary shows order count, totals by currency, last order date and refunded orders, then opportunities and cases, and ends with two sentences on what the picture suggests. It only reads and never adds amounts in different currencies.

Business outcome

---

Agents go into a call knowing orders, open pipeline and open cases, with totals kept by currency.
See Full Use Case

scenario

-

Support answers an order question without knowing the buyer's open cases, tasks or recent calls in the CRM, so replies contradict what sales already said. Connecting a CRM item to an order by guesswork makes it worse.

What popdock provides

--

Give a BigCommerce order number and it reads the order, with status, payment, shipping, refunds and its line items. It then finds the buyer in Capsule CRM by the billing email, reads the owner, the last 10 entries, open cases and open tasks, and keeps only items that are not closed or completed. It suggests a reply based only on what was found. It only reads, stops if the order or contact is missing or ambiguous, and links CRM items to the order only with evidence.

Business outcome

---

Support replies with the order and the buyer's CRM history in view, so they do not contradict what sales has said.
See Full Use Case

scenario

-

Collections and account managers look up a customer's store orders in one system and their balance in another. An account that keeps ordering while overdue can go unnoticed, and ids from the two systems are unrelated numbering that cannot be compared.

What popdock provides

--

Give a customer email and optionally a lookback in days, and it finds the customer in BigCommerce, then totals orders, spend, refunds and order statuses. It finds the Intacct customer by company or name, preferring the one whose email matches and stopping with candidates if none does. It then shows status, terms, credit limit, total due and open invoices, oldest first, and flags balance over the credit limit, overdue invoices while orders arrive, and an inactive status. It only reads and never adds mixed currencies.

Business outcome

---

Overdue accounts that keep ordering are caught, with both sides shown in their own currency and no ids compared.
See Full Use Case

scenario

-

Chasing a customer payment needs order history from the store and open invoices from the ERP, pulled separately. A store order marked paid can still have an open ERP invoice, and that mismatch is easy to miss when comparing two screens.

What popdock provides

--

Give a customer email and optionally a lookback in days, and it finds the customer and recent orders in BigCommerce. It then finds the NetSuite customer by email and reads balance, open invoices, open receivable items and recent payments. The summary shows total ordered, invoiced, unpaid and the NetSuite balance, and points out paid store orders that still have an open invoice for a similar amount. It only reads, reports one side alone if the other is missing, and stops on duplicate NetSuite matches.

Business outcome

---

Payment chasing starts from both systems at once, with paid-but-open mismatches pointed out.
See Full Use Case

scenario

-

Merchandisers sort a product export by sold count and then hunt for stale stock separately. Without a clear cut-off, older products that have never sold are mixed in with new arrivals, and a revenue guess from units sold can mislead.

What popdock provides

--

Optionally give how many products to rank and a brand, and it resolves the brand first, listing the options and stopping if several match. It reads visible BigCommerce products with at least one sale and ranks them by units sold, then reads visible products created more than 90 days ago that have never sold. Both tables show price and stock, followed by a few observations such as high stock with no sales. It only reads, ranks on units sold alone and shows the price used if it estimates revenue.

Business outcome

---

Merchandisers see what sells and what has stalled in one answer, with older stock that never sold separated from new arrivals.
See Full Use Case

scenario

-

Finance reconciles refunds by exporting orders and matching them to lines manually. Without a fixed period the numbers shift between runs, and it is hard to see which payment method, channel or product the refunds cluster around.

What popdock provides

--

Give a start date, an end date and optionally a minimum refund, and it reads the BigCommerce orders in that period with refunds at or above the minimum. It totals refunded against order value, works out the refund rate, and breaks refunds down by payment method, channel and billing country. For the 10 largest refunds it reads the refunded items, then reports the headline rate, tables, most refunded products and any pattern worth a follow-up. It requires an explicit period, shows the basis for each rate and only reads.

Business outcome

---

Refunds for a period are totalled, broken down and traced to products without a manual export.
See Full Use Case

scenario

-

Understanding how a BigCommerce store is set up means clicking through store settings, channels, sites, pages and shipping zones one screen at a time. Integrators and new admins end up with notes spread across tabs, and a disabled channel or a hidden homepage is easy to miss.

What popdock provides

--

Ask for a snapshot, optionally limited to one channel. It reads the store details, each channel and its site, the pages by type and visibility, and the shipping zones, then puts them in one compact summary. It lists concerns such as disabled channels that still have sites, channels with no site, no enabled shipping zone and a hidden homepage. Nothing is changed, it only flags concerns, and if a read returns no records or hits the record limit it says so instead of inventing figures.

Business outcome

---

You get one readable picture of how the store is configured, with concerns flagged and nothing changed, instead of a tour of settings screens.
See Full Use Case

scenario

-

Marketing tallies new newsletter sign-ups from exports to see which sources and channels bring people in. Counting by source, channel and week in a spreadsheet is slow, and the export carries every subscriber email whether the report needs it or not.

What popdock provides

--

Give a start and end date and it reads the BigCommerce subscribers added in that period. It counts them by source, by channel and by week, and works out the share linked to an order from checkout. The report leads with a total and shows tables for each breakdown. Subscriber emails are left out unless you ask for them, nothing is changed, and if no records come back or the record limit is hit it says so and suggests a narrower filter.

Business outcome

---

You see which sources, channels and weeks drive sign-ups without handling an export, and subscriber emails stay out of the report by default.
See Full Use Case

scenario

-

A rep checks the store admin for a buyer, then searches Dynamics 365 Sales by hand for the matching contact or account. Open opportunities and cases are easy to miss, and a similar name can send the rep to the wrong record.

What popdock provides

--

Give a customer email and optionally how many orders to look back. It finds the customer in BigCommerce, reads their recent orders for count, total spend and latest order date, then looks for the matching Dynamics 365 Sales contact, and the account by company name if email finds nothing. It adds open opportunities and cases, and states which match basis it used. If several customers match it lists them and stops, and if there is no CRM record it says so. If the systems disagree on name or phone it shows both. Nothing is written.

Business outcome

---

A rep sees the buyer, their orders and their CRM deals and cases in one profile, with the match basis stated and no guessed records.
See Full Use Case

scenario

-

Confirming that a web order became a NetSuite sales order means searching both systems by customer, date and total. A missing customer, a duplicate customer or a total that is a few cents off is easy to overlook, and cancelled orders look like gaps.

What popdock provides

--

Give a BigCommerce order number and optionally a date window. It reads the order and its lines, finds the NetSuite customer by billing email, then looks for a sales order within the window that matches the total. It compares totals and the line items by SKU and reports the difference. It stops if the order is not found, the customer is missing, or several customers match. Incomplete or cancelled orders are called expected gaps, totals within a cent count as a match, and nothing is changed in either system.

Business outcome

---

You know whether a web order reached NetSuite and whether the totals and lines agree, without searching two systems by hand.
See Full Use Case

scenario

-

Stock and prices are compared between the store and the ERP by hand, so a product can stay on sale with no stock or sell below cost. Checking one SKU means opening the product in BigCommerce, the item in Intacct and each warehouse.

What popdock provides

--

Give a SKU and optionally one warehouse. It reads the product from BigCommerce, including its variants if needed, and the Intacct item with the same ID, then the warehouse quantities. One table sets store against ERP for name, price, cost and stock, and flags stock that differs, a product sold as available with no uncommitted stock, a price below cost and an inactive item still visible. It stops if the item ID pattern differs rather than guessing, skips stock when tracking is off, and changes nothing.

Business outcome

---

You see in one table where store stock and price disagree with the ERP, before a product sells with no stock or below cost.
See Full Use Case

scenario

-

Products are set up in the store and again in the ledger, and the two catalogues drift apart. Invoices then carry the wrong product or price, and finding the gaps means lining up two lists by name.

What popdock provides

--

Give a minimum number of units sold and it reads the visible BigCommerce products that meet it, then the Rillet product list. It matches by exact name first, then by SKU appearing in the Rillet name or description, and marks each product Matched, Price differs or Missing, noting inactive Rillet products. The report lists Missing and Price differs products by units sold, with counts. Name-only matches are labelled as suggestions, ids and amounts are quoted as returned, it stops if either side is empty, and no products are created.

Business outcome

---

You see which best-selling store products are missing or priced differently in the ledger, with weak matches labelled and nothing created.
See Full Use Case

scenario

-

At month end finance compares storefront refunds with ERP credit memos by hand. A refund with no credit memo overstates revenue, and an order that was never invoiced looks like a gap when it is not.

What popdock provides

--

Give a start date and optionally a Business Central company. It lists the refunded BigCommerce orders since then and looks for a posted credit memo for each. If none is found it checks whether the sale was ever invoiced, then looks for a credit memo filed under a different reference. Each order is marked Matched, Amount differs, Missing credit memo or Never invoiced, with counts and the refunded value with no credit memo. One cent of rounding is tolerated, partial refunds show both amounts, and nothing is changed.

Business outcome

---

Finance sees which refunds lack a credit memo and by how much, with never invoiced orders kept apart, before revenue is overstated.
See Full Use Case

scenario

-

Refunds issued in the store are not always reflected as credit memos in the ledger, so revenue stays overstated until someone notices. Matching them by hand means lining up customer, amount and currency across two systems.

What popdock provides

--

Give a start date and optionally a minimum refund amount. It lists the refunded BigCommerce orders, reads the Rillet credit memos, and maps each billing email to a Rillet customer. Each order is marked Credited, Amount differs or No credit memo by comparing customer, amount within a cent and currency. A credit memo that could cover several orders is listed against each and flagged as ambiguous, and customers missing in Rillet are marked and skipped. Amounts are quoted as returned, nothing is guessed, and no credit memos are created or applied.

Business outcome

---

You see which store refunds have no credit memo in Rillet, with ambiguous matches flagged and nothing created or applied.
See Full Use Case

scenario

-

Operations often learn that a destination is not covered only when a customer cannot check out. Checking by hand means reading each shipping zone's locations and then working out which countries recent orders came from.

What popdock provides

--

Give a lookback period or accept 90 days. It reads the enabled shipping zones with their locations, type and free shipping setting, then reads recent orders for billing country and order total. The report shows orders and revenue per billing country, countries that appear in no enabled zone, and zones that had no orders. It states that billing country is only a proxy for the shipping destination. Nothing is changed, and if no records are returned or the record limit is hit it says so.

Business outcome

---

You find uncovered destinations and unused zones before a customer hits a dead end at checkout, with the billing country proxy stated.
See Full Use Case

scenario

-

Before sending a quote, a rep checks each item in the store admin for stock and price. It is slow, it gets skipped under pressure, and a quote then goes out for something that is hidden, short or not in the store at all.

What popdock provides

--

Give a Dynamics 365 Sales quote name. It reads the quote and its lines, then looks up each product in BigCommerce by SKU, and by name if the SKU finds nothing. For each line it reports visibility, inventory level and store price, with a status of OK, Short on stock, Not visible or Not in store. Name-only matches are marked as weaker. It stops if several quotes share the name or the quote has no lines, and it reads only, with nothing changed in either system.

Business outcome

---

A rep knows before sending whether every quoted item is visible, in stock and priced as expected, without opening the store admin.
See Full Use Case

scenario

-

Large BigCommerce orders are rarely checked against who owns the buyer in HubSpot, so big buyers can have no owner and no recent follow-up. Finding them means exporting orders and searching HubSpot contact by contact.

What popdock provides

--

Give an order total threshold and optionally a lookback period. It reads the recent BigCommerce orders over that total, then looks up each distinct billing email in HubSpot for owner, lifecycle stage, lead status and last activity. If the contact has a company it lists the open deals. The report is ordered by order total and flags buyers with no contact, no owner or no activity in 90 days. Several orders from one email share one lookup, nothing is changed, and if no orders qualify it suggests a lower threshold.

Business outcome

---

Sales sees which large buyers have no HubSpot owner or have gone quiet, so no big order goes without a follow-up.
See Full Use Case

scenario

-

Managers cannot tell whether deals won in Nutshell turned into real store revenue without matching leads to customers by hand. It means reading each lead, finding the person's email, searching BigCommerce and adding up orders since the win.

What popdock provides

--

Give a lookback period and a maximum number of leads. It lists the won Nutshell leads, reads the first person on each for an email, and finds the BigCommerce customer by email, then by company name. It sums the orders placed since the close date and groups leads into ordered, no order yet and not in store, with counts. If the won status filter is rejected it falls back to reading leads without it. Differing currencies are flagged as not comparable, and nothing is changed.

Business outcome

---

Managers see which won deals became store revenue, which have not ordered yet and which are not customers, without matching by hand.
See Full Use Case

scenario

-

Managers cannot tell whether deals won in Pipedrive turned into real store revenue without matching them by hand. It means reading each deal, finding the person's email, searching BigCommerce and adding up orders since the win.

What popdock provides

--

Give a lookback period and a maximum number of deals. It lists the won Pipedrive deals, finds each person's email, and matches a BigCommerce customer by email, then by organization name. It sums the orders placed since the win date and groups deals into ordered, no order yet and not in store, with counts. If the won status filter is rejected it falls back to reading deals without it. Differing currencies are flagged as not comparable, people sharing a name are separated by organization, and nothing is changed.

Business outcome

---

Managers see which won deals became store revenue, which have not ordered yet and which are not customers, without matching by hand.
See Full Use Case

scenario

-

Before an account call, a rep checks Nutshell for the contacts and leads, then searches the store separately to learn what the account really buys. Buyers who are not in the CRM, and contacts who never bought, are easy to miss.

What popdock provides

--

Give a Nutshell account name and optionally a lookback period. It finds the account, reads its contacts and leads, then finds the matching BigCommerce customers by email and by company name. It reads their orders for the period and reports the owner, last contacted date, open leads, total spend, order count and spend per person. It lists store buyers who are not CRM contacts and contacts who have never bought, and refuses an ambiguous account name. Nothing is changed.

Business outcome

---

A rep walks into the account call knowing what the account buys, who buys it and whether the follow-up matches the buying.
See Full Use Case

scenario

-

Stock and price for a SKU are checked by hand in the storefront and again in NetSuite, and the two drift apart unnoticed. NetSuite can also hold several pricing rows and locations, which makes the right number hard to find.

What popdock provides

--

Give a SKU and optionally a NetSuite price level. It reads the BigCommerce product for price, cost, stock and visibility, then the NetSuite item, its quantity by location and its pricing rows, taking the base price as the row with the lowest minimum quantity. It compares stock and price and gives a short table with a flag and a one-line verdict. If the SKU is missing on one side it says which and skips the comparison, it shows all pricing rows when there are several, and nothing is changed.

Business outcome

---

You see whether a SKU's stock and price agree between the store and NetSuite, and which side is missing it, without opening both systems.
See Full Use Case

scenario

-

Prices and stock for the same item are kept in the store and in Dynamics 365 Sales, and nobody notices when they drift apart. Comparing means opening the product in both places and then each CRM price list.

What popdock provides

--

Give a product name and optionally a price tolerance. It finds the product in BigCommerce and its variants, then the Dynamics 365 Sales product and its price list amounts. It sets BigCommerce price, sale price and inventory beside the CRM list price, price list amounts, status and quantity on hand, and flags differences above the tolerance. It stops if several products match, notes when a SKU confirms the match, skips the percentage check across currencies, and changes nothing.

Business outcome

---

You see where the store and the CRM disagree on price or availability for a product, with ambiguous matches never guessed.
See Full Use Case

scenario

-

Catalog and price drift between the store and Salesforce is often found only when a quote goes out wrong. Checking one SKU means opening the BigCommerce product, the Salesforce product and each price book entry.

What popdock provides

--

Give a SKU. It looks up the product in BigCommerce and the Salesforce product by SKU or product code, then reads its price book entries. It compares name, active or visible status and price, naming each price book, and says whether the product is in both systems or only one. It stops on no match or several matches, reports a missing side or a missing price book entry plainly, treats price book differences as informational because they can be legitimate, and changes nothing.

Business outcome

---

You see whether a product agrees between the store and Salesforce, and which side is missing it, before a quote goes out wrong.
See Full Use Case

scenario

-

Month-end tie-out of store sales to booked revenue is done with two exports and a pivot table, and gaps are found days after close. Mixed currencies and refunds make the sums easy to get wrong.

What popdock provides

--

Give a start and end date and optionally one currency. It totals BigCommerce orders, tax and refunds per currency, then the Rillet invoices and credit memos for the same range, and reports store net, ledger net, the difference and the percentage gap per currency. It lists the five largest store orders for you to check against invoices. Currencies are never added together, a partial sum is flagged when the order limit is hit, timing differences are offered as a possible reason, and nothing is changed.

Business outcome

---

Finance sees the gap between store sales and invoiced revenue per currency at tie-out, without two exports and a pivot table.
See Full Use Case

scenario

-

Campaign revenue is guessed by exporting the people who clicked and matching them to orders in a spreadsheet. The match is slow, and it is easy to count orders from before the click or to claim more than the data shows.

What popdock provides

--

Give a Constant Contact campaign and optionally a window in days. It confirms the campaign exists, reads the clicks, and matches each unique clicker to a BigCommerce customer by email, ignoring case. It then finds orders placed within the window after the first click. The report gives unique clickers, clickers who are customers, clickers who ordered, order count and value, with a table by clicker. It states that this shows association in time, not that the campaign caused the order, and it stops on an unknown campaign or no clicks. Nothing is changed.

Business outcome

---

Marketing sees which clickers bought and how much within the window, with the association stated honestly rather than claimed as cause.
See Full Use Case

scenario

-

People unsubscribe from Constant Contact campaigns but stay on the store newsletter, so they keep getting email. Because the two systems are never compared, nobody notices until a customer complains.

What popdock provides

--

Give a start date or accept 90 days. It reads the recent Constant Contact unsubscribes with reason and date, matches each unique email to a BigCommerce customer, and reads their orders since the unsubscribe. It also checks whether the address is still a BigCommerce newsletter subscriber. The report highlights rows still subscribed, which a person needs to action. It never removes or changes a subscriber, counts emails with no customer without listing them, and stops if there are no unsubscribes.

Business outcome

---

Marketing sees who unsubscribed yet is still subscribed in the store, so their choice is respected, with nothing removed automatically.
See Full Use Case

scenario

-

To answer an order question, support and account managers switch between the store admin and Capsule CRM to understand the customer. Open opportunities, cases and tasks are easy to miss, and a refund with no follow-up task goes unnoticed.

What popdock provides

--

Give a customer email and optionally a lookback period. It finds the customer in BigCommerce and reads their recent orders with status, totals and refunds, then finds the same email in Capsule CRM. It adds opportunities, cases and open tasks, and ends with two sentences on the next step for the owner. It stops if the customer is ambiguous, shows the orders and reports the customer as absent from Capsule CRM if there is no match, and says none found for empty sections. Nothing is changed.

Business outcome

---

Support and account managers see orders and CRM context together, so a refund with no open task or a live deal is not missed.
See Full Use Case

scenario

-

Answering what happened with order 1234 means opening the order, its items and the customer on three screens and doing the sums by eye. Refunds, partial shipments and discounts that exceed the subtotal are easy to overlook.

What popdock provides

--

Give an order number. It reads the order, its items and the customer, or notes that it was a guest order. It explains status, payment status, payment method and dates, then the money: subtotal, tax, shipping, discount, total and refunded amount. It lists the items, checks whether items shipped match the item count, and points out anything odd such as a refund, no shipped items on an old order or a discount larger than the subtotal. It stops if the order is not found, changes nothing, and says if the record limit is hit.

Business outcome

---

A support agent gets a plain language account of an order, with anything unusual called out, without opening three screens.
See Full Use Case

scenario

-

New store customers never reach the CRM, so nobody follows them up. Finding them means exporting the store customer list and checking Capsule CRM contacts one by one by email.

What popdock provides

--

Give a start date and a maximum number of customers, or accept 30 days and 50. It lists the new BigCommerce customers and checks each email in Capsule CRM, ignoring case. It reports counts for checked, found, missing and cannot check, with customers lacking an email kept separate, then a table of the missing ones with their order count and latest order total. If the limit is reached it says there may be more and suggests a narrower date range. Nothing is changed, and it points you to the separate add contact job for any you want to add.

Business outcome

---

Sales sees which new store customers have no Capsule CRM contact and what they have bought, so none go without follow-up.
See Full Use Case

scenario

-

Finding store buyers who never made it into Drip means exporting orders, pulling out the emails and searching Drip for each one. Guest checkouts and mistyped addresses slip through, and the buyers who spent the most can go unnoticed.

What popdock provides

--

Say how far back to look and, if you want, a minimum order value, and it reads recent BigCommerce orders, groups them by customer and looks each customer's email up in Drip. It lists the customers with no matching Drip subscriber, ranked by spend. Guest orders are skipped and counted, customers without an email are listed separately, and it checks at most 50 customers and says how many were left out. Nothing is changed in either system.

Business outcome

---

You see which paying BigCommerce customers are missing from Drip, ranked by spend, without exporting or comparing anything by hand.
See Full Use Case

scenario

-

Someone exports new store customers and then searches Dynamics 365 Sales for each one, first as a contact and then as a lead. It is slow, so shoppers who never reached the sales pipeline are easy to miss.

What popdock provides

--

Say how far back to look and how many customers to check, and it lists new BigCommerce customers, then looks each email up in Dynamics 365 Sales contacts and, if none is found, in leads. Each customer is classed as contact found, lead only or missing, with counts for each. It only reads, compares emails regardless of case, caps how many customers it checks, and stops if BigCommerce returns no new customers.

Business outcome

---

You see which new store customers are not yet contacts in Dynamics 365 Sales, so none are missed by the sales team.
See Full Use Case

scenario

-

New store customers are not created in the ERP until an invoice fails, and by then nobody knows who is missing. Checking by hand means matching BigCommerce names against Intacct customers, where company spellings rarely agree.

What popdock provides

--

Say how far back to look and it reads new BigCommerce customers, then searches Intacct for a customer matching each company or name. Near matches are reported separately as possible duplicates with their Intacct customer ID, and for the customers that are missing it adds order count and spend from BigCommerce. It reads only and creates nothing, caps the list at 50 and says so, and marks customers with a common name and no company as unverified rather than missing.

Business outcome

---

Operations sees which store customers have no Intacct record, ranked by spend, before an invoice fails.
See Full Use Case

scenario

-

Someone exports new store customers and searches Nutshell for each one by hand. Names are spelled differently in each system, so shoppers who never reached the sales pipeline are easy to miss and real matches can look like gaps.

What popdock provides

--

Say how many days back to look and how many customers to check, and it lists new BigCommerce customers, then searches Nutshell by name and confirms each match by email. If the name search finds nothing it tries the last name before calling a customer missing. Matches with a different name spelling, and customers with no email who can only be matched by name, are listed separately as weak matches. It only reads, and keeps to the number of customers you asked for.

Business outcome

---

You get a list of new store customers with no Nutshell contact, with weak matches set apart, so reps can follow up on real gaps.
See Full Use Case

scenario

-

Someone exports new store customers and searches Pipedrive for each one by hand, so shoppers never reach the sales pipeline. A customer with no email or a different spelling of the name is easy to call missing when they are already there.

What popdock provides

--

Say how many days back to look and how many customers to check, and it lists new BigCommerce customers, then looks each email up among Pipedrive persons. A customer with no email, or no hit on email, is tried by name and any hit is marked a weak match. It lists the customers with no Pipedrive person, with counts of checked, matched and missing, and sets weak matches apart as possible duplicates. It only reads and keeps to the number of customers requested.

Business outcome

---

Reps see which new store customers are not yet Pipedrive persons, with weak matches set apart so real gaps are clear.
See Full Use Case

scenario

-

Finance exports store customers and ledger customers to spreadsheets and compares them by eye. New buyers are missing from the books by the time the first invoice is due, and a changed email on the same name looks like a new customer.

What popdock provides

--

Give a start date, and optionally a company filter, and it reads recent BigCommerce customers and the customer lists in Rillet. Each store customer is matched on email first, then on name or company, and marked matched, name-only match or missing from Rillet. It reads only, never guesses a match, quotes IDs exactly as returned, and stops with a clear message if either side comes back empty instead of calling everyone missing.

Business outcome

---

Finance sees which store customers are not yet in Rillet, with name-only matches kept apart, before the first invoice is due.
See Full Use Case

scenario

-

New store customers never reach the CRM, and finding them means exporting emails and searching Salesforce one at a time. Contacts and leads both have to be checked, and customers with no email cannot be matched at all.

What popdock provides

--

Say how far back to look and how many customers to check, and it reads recent BigCommerce customers, then checks each email against Salesforce contacts and, if none matches, against leads. Customers are marked in contacts, in leads or missing, and those with no email are listed separately as unmatchable. It only reads, creates no leads, compares emails regardless of case, and says when the customer limit was reached so the list may be incomplete.

Business outcome

---

You get a clear list of store customers missing from Salesforce, ready for follow up, without searching one by one.
See Full Use Case

scenario

-

Support does not know which unhappy customers are also big spenders, because order data lives in BigCommerce and cases live in Dynamics 365 Sales. Matching them means totalling orders by email and then searching for cases customer by customer.

What popdock provides

--

Give a minimum order value and a start date, and it finds BigCommerce orders at or above that value, groups them by billing email and totals spend per customer. It looks each customer up in Dynamics 365 Sales and reads their active cases. You get the customers with open cases ranked by spend, with open case count, priority and oldest case title, plus a separate list of high spenders not found in the CRM. It only reads, and stops if no orders qualify.

Business outcome

---

Support sees which high-value store customers have open cases, ranked by spend, so service can prioritize valuable accounts.
See Full Use Case

scenario

-

Someone exports recent orders and searches Business Central for each one, and orders that never synced are noticed only when a customer complains. With hundreds of orders, a lookup that errors is easily mistaken for a missing order.

What popdock provides

--

Give a start date and an order status and it lists matching BigCommerce orders, then checks each against Business Central sales documents and, if none is found, posted sales invoices. An order is reported missing only when both come back empty, and a lookup that errors is reported as unchecked instead. It reads only, tells you when the list may be truncated, checks at most 50 orders and says how many were left, and totals the value missing.

Business outcome

---

Operations finds orders that never reached Business Central, with the missing value totalled, before a customer has to complain.
See Full Use Case

scenario

-

Web orders that never reached the ERP are found only when a customer complains or the books fail to tie. Checking by hand means searching Dynamics GP for each order number and comparing the amounts on both sides.

What popdock provides

--

Give a start date and optionally an order status and a limit, and it lists BigCommerce orders, then looks each one up in Dynamics GP by customer PO number, which holds the order number. Orders with no sales document are reported missing, and found orders whose amount differs from the order total by more than a cent are flagged. It reads only, and if nearly every order shows as missing it warns that Dynamics GP probably uses a different numbering convention.

Business outcome

---

Finance finds web orders missing from Dynamics GP and amount mismatches before the books fail to tie.
See Full Use Case

scenario

-

Support and fulfilment staff scan the order screen for stuck orders, and the unpaid, refunded or part-shipped ones are easy to miss. Each person applies their own idea of what counts as a problem, so the same order is flagged by one and ignored by another.

What popdock provides

--

Say how far back to look, and optionally a channel, and it reads recent BigCommerce orders and checks the real status values before deciding what counts as a problem. It flags orders that are not fully paid, have a refund, have not shipped after more than 3 days, or are marked shipped with fewer items shipped than ordered. The result is grouped by reason, oldest first. It only reads, changes no order and contacts no customer, and says when a result may be incomplete.

Business outcome

---

Operations gets one consistent list of orders that need follow up, so unpaid, refunded and part-shipped orders are not missed.
See Full Use Case

scenario

-

Refunds happen in BigCommerce while support tickets live in HubSpot, so refunded buyers can go without a follow up. Finding them means listing refunded orders and searching HubSpot for each buyer's tickets.

What popdock provides

--

Say how far back to look and a minimum refund, and it finds refunded BigCommerce orders, then looks up each buyer's HubSpot contact by billing email and reads any tickets created since the order date. Each order is shown with a ticket status of none, open, closed or no contact, with orders that have no ticket first. It only reads, writes no tickets or notes, caps the list at 50 orders and lists orders with no billing email as unmatchable.

Business outcome

---

Support sees which refunded buyers have no HubSpot ticket, so none go without follow up.
See Full Use Case

scenario

-

Store stock drifts from ERP quantities, and the first sign is an oversell or a lost sale. Comparing means looking up each product's SKU in Dynamics GP, adding up quantities across locations and subtracting what is already allocated.

What popdock provides

--

Say the smallest difference that matters, optionally one SKU, and how many products to check, and it reads BigCommerce products and looks each SKU up in Dynamics GP. It sums quantity on hand, subtracts the allocated quantity and compares with the store level. You get mismatches sorted by size of difference, SKUs not in Dynamics GP, and counts of products checked. It only reads, skips products with no SKU, and says how many were checked because the list stops at the limit.

Business outcome

---

Operations sees which products have store stock that differs from Dynamics GP before it causes an oversell.
See Full Use Case

scenario

-

New store subscribers never reach the Mailchimp audience, so campaigns miss them. Checking means exporting the store list and searching the audience for each address, and re-adding someone who already unsubscribed creates a compliance problem.

What popdock provides

--

Give the audience name and how far back to look, and it reads recent BigCommerce newsletter subscribers. It first confirms the audience is unique, and stops and lists the matches if there are none or several. It then checks each subscriber, at most 50, and reports those missing and those present with a status other than subscribed. It only reads, adds no one, never suggests re-adding someone unsubscribed or cleaned, and says when only the first 50 were checked.

Business outcome

---

Marketing sees which store subscribers are missing from the audience while leaving alone anyone who opted out.
See Full Use Case

scenario

-

Accounting-system customers who could buy online have no store account, and nobody knows who they are. Working it out by hand means pulling a customer class from Dynamics GP and searching BigCommerce for each email.

What popdock provides

--

Give a customer class and how many customers to check, and it lists active Dynamics GP customers in that class, setting aside any with no email and counting them. It looks each remaining email up in BigCommerce, ignoring case, and lists the customers with no store account with ID, name, email and city. It only reads, stops if Dynamics GP returns no customers, and reminds you that a missing customer may be a wholesale account that never shops online.

Business outcome

---

Sales sees which active ERP customers have no BigCommerce account, so it can invite them to buy online.
See Full Use Case

scenario

-

Abandoned carts are chased without checking whether the buyer already ordered or has unsubscribed. The cart lives in Mailchimp and the order in BigCommerce, so a reminder can land on someone who bought an hour later or opted out.

What popdock provides

--

Say how far back to look and an optional minimum cart value, and it reads recent Mailchimp abandoned carts and checks BigCommerce for an order by the same email since the cart was created. For carts with no order it notes whether the person is a known customer and their Mailchimp status. It flags unsubscribed people as not to be contacted, lists carts with no email as unmatched, checks at most 30 carts, and only reads. Nothing is sent or changed.

Business outcome

---

Sales chases only carts that are still unconverted, and never contacts people who have unsubscribed.
See Full Use Case

scenario

-

People who unsubscribe in Mailchimp can stay on the store newsletter list, which risks compliance complaints. Spotting them means exporting unsubscribes and searching the BigCommerce subscriber list address by address.

What popdock provides

--

Say how far back to look, and optionally one campaign, and it reads Mailchimp unsubscribes, then looks up each distinct email, at most 50, among BigCommerce subscribers. It lists those still subscribed in BigCommerce with the unsubscribe date, reason and subscriber ID, and counts those checked, still subscribed and not in the store. It only reads, never deletes or updates subscribers, says when only the first 50 were checked, and leaves removal to the store owner.

Business outcome

---

Marketing sees who opted out in Mailchimp but is still on the store list, so they can be removed before a complaint.
See Full Use Case

scenario

-

New store customers are copied into the ERP by hand, and some never get created. Checking means searching NetSuite for each BigCommerce customer's email, and duplicates or missing emails make the result hard to trust.

What popdock provides

--

Give a start date and how many customers to check, and it lists new BigCommerce customers, then looks each email up in NetSuite. You get three lists: matched with the NetSuite internal ID, missing from NetSuite, and unmatchable because there is no email. If NetSuite returns several customers for one email it marks it as a duplicate and lists the IDs. It only reads, creates no customers, and stops if BigCommerce returns none.

Business outcome

---

You see which new store customers are not yet in NetSuite, with duplicates and no-email cases kept apart.
See Full Use Case

scenario

-

Credit controllers learn that an overdue customer has fresh orders only after they ship. Linking the two means pulling debtors from Intacct and then hunting for each one in BigCommerce, where names rarely match exactly.

What popdock provides

--

Give a minimum amount owed and how far back to look, and it reads active Intacct customers owing at least that, working on up to 30 with the largest balances. It finds each in BigCommerce by company or name, reads their recent orders and keeps those not yet shipped, completed, cancelled or refunded. You get customers with open orders, over-limit ones first. It only reads, never holds or changes an order, lists ambiguous matches instead of guessing, and notes mixed currencies.

Business outcome

---

Credit control sees overdue customers with open store orders before more is shipped.
See Full Use Case

scenario

-

Account teams rank top spenders from order exports and then check each one in the email tool by hand. Disengaged big customers go unnoticed because nobody looks up their subscription status, lead score and campaigns.

What popdock provides

--

Say how many top customers and how far back to look, and it reads BigCommerce orders, totals spend by customer, ignores guest orders and keeps the top ones. It looks each up in Drip by email and shows status, lead score and the number of active campaigns. Each row is marked not in Drip, not active, no campaigns or engaged, with counts. It only reads, and a customer with no email is shown as unknown instead of guessed.

Business outcome

---

Account teams see which top spenders are not engaged in Drip, so they can follow up with the right people.
See Full Use Case

scenario

-

Reps cannot see which heavy buyers in the store have no active deal in the CRM, so repeat revenue goes unworked. Ranking buyers means netting refunds out of order exports, then searching Nutshell for each contact and any open lead.

What popdock provides

--

Say how many top customers and how far back to look, and it reads up to 250 BigCommerce orders, totals spend per customer less refunds and ignores guest orders. For each top customer it finds the Nutshell contact, confirms the match by email and checks for an open lead. It lists customers with no contact or no open lead, ranked by net spend, and briefly lists those who do have a lead. It only reads, and warns when the order cap may have truncated the ranking.

Business outcome

---

Reps see which heavy store buyers have no open Nutshell lead, so repeat revenue gets worked.
See Full Use Case

scenario

-

Reps cannot see which heavy buyers in the store have no active deal in the CRM, so repeat revenue goes unworked. Ranking buyers means netting refunds out of order exports, then searching Pipedrive for each person and their open deals.

What popdock provides

--

Say how many top customers and how far back to look, and it reads up to 250 BigCommerce orders, totals spend per customer less refunds and ignores guest orders. For each top customer it finds the Pipedrive person by email, checks the open deal count and confirms it with a deal lookup. It lists customers with no person or no open deal, ranked by net spend, and briefly lists those who do have a deal. It only reads, and warns when the order cap may have truncated the ranking.

Business outcome

---

Reps see which heavy store buyers have no open Pipedrive deal, so repeat revenue gets worked.
See Full Use Case

scenario

-

People who opted out in Drip can still be emailed from other tools because nobody checks them against store orders. A recent buyer who unsubscribed looks like any other customer in the order list.

What popdock provides

--

Say how far back to look and how many unsubscribed people to check, and it reads people in Drip with an unsubscribed status, finds each in BigCommerce by email and reads their recent orders. You get a table of unsubscribed people who have bought recently with order count, spend and latest order date, plus counts of those with no store customer or no recent orders. It only reads, never suggests re-subscribing anyone, and stops if nobody is unsubscribed.

Business outcome

---

Marketing sees which opted-out people are still buying, so their choice is respected and service messages use the right channel.
See Full Use Case

scenario

-

Large storefront orders land in BigCommerce while the sales team works from Capsule CRM. Someone has to filter the orders above a threshold, look up each buyer by email in the CRM and check for open deals. It is easy to chase a buyer who is already in a deal, or to miss a big buyer who is not in the CRM at all.

What popdock provides

--

Give a minimum order total and optionally a start date, and it finds BigCommerce orders at or above that amount, defaulting to the last 30 days. It checks each buyer's email in Capsule CRM for a contact, the owner and any opportunities, counting only those that match the contact and are not closed. Orders are grouped into buyer not in the CRM, in the CRM with no open opportunity, and with an open opportunity, with a total for each group. Currencies are kept separate and nothing is changed in either system.

Business outcome

---

Sales sees which large orders need follow-up and which buyers are already in a deal, with currencies kept apart and nothing changed.
See Full Use Case

scenario

-

A rep checking a store customer against the CRM has BigCommerce open in one tab and Salesforce in another, copying an email across and comparing names, phones and companies by eye. Mismatched details and duplicate Salesforce records go unnoticed until someone emails the wrong person.

What popdock provides

--

Give a customer email and it looks up the customer in BigCommerce, then finds the matching Salesforce contact, or a lead if there is no contact, and the account when the customer has a company. It tables name, phone, email, company and owner side by side with a match flag and says whether the person is a contact, a lead only, an account only or not in Salesforce. If more than one record matches it lists them and flags the duplicate, and on an error it names the system and stops. It only reads and nothing is changed.

Business outcome

---

Reps see every field difference between the store customer and the Salesforce record in one table, and duplicates are flagged before anyone acts.
See Full Use Case

scenario

-

Account managers compare a store customer and the CRM contact by opening both screens side by side. Stale phone numbers, wrong companies and duplicate contacts slip through because nobody reads every field on both sides.

What popdock provides

--

Give an email address and it finds that customer in BigCommerce and the same contact in Capsule CRM. It matches on email and says when it had to fall back to the name. It tables name, email, phone and company with a status of match, differs or missing on one side, and adds the Capsule CRM owner and last contacted date. If more than one record matches it lists them and stops rather than guessing. It ignores differences in letter case, spacing and phone punctuation and tells you it did, and nothing is changed.

Business outcome

---

You see exactly which details differ between the store customer and the Capsule CRM contact, without guessing between duplicates.
See Full Use Case

scenario

-

To check that a customer was set up the same way in both places, someone opens the BigCommerce admin and Business Central side by side. Mismatched emails, phone numbers or a blocked flag are easy to miss, and the account balance sits on a different screen again.

What popdock provides

--

Give an email address, and optionally a company, and it finds the customer in BigCommerce and the customer in Business Central. It tables name, email, phone, company, city and state, and blocked status, with the Business Central balance, balance due, credit limit and posting group, and marks each row as a match or a difference. If more than one record matches it lists them and asks which one rather than guessing. Fields missing on one side show as not available, and nothing is changed in either system.

Business outcome

---

Operations sees every setup difference and the Business Central balance for one customer in a single table, with no guessing between look-alikes.
See Full Use Case

scenario

-

Checking whether a shopper record matches between the store and the ERP means opening both systems and eyeballing fields. Mismatched phone numbers or names go unnoticed, and a support agent may quote the wrong details to a customer.

What popdock provides

--

Give an email address and it finds the customer in BigCommerce and in NetSuite, trimming spaces and ignoring case when matching. It compares name, first name, phone and email, normalising phone numbers to digits, and shows the NetSuite balance. If more than one customer matches in either system it lists them and stops. A field that is empty on one side is reported as missing rather than a mismatch, a customer found in neither system is stated plainly, and nothing is changed.

Business outcome

---

Support sees whether the store customer and the NetSuite customer agree, and what is missing, from one table instead of two systems.
See Full Use Case

scenario

-

Finance compares a web order against the sales order or invoice in the CRM by switching between two screens. Totals that do not agree are easy to miss, especially when the CRM record sits under the parent account rather than the buyer's name.

What popdock provides

--

Give a BigCommerce order id, and optionally an amount tolerance, and it reads the order and its line items, then finds the customer in Dynamics 365 Sales by billing email or company. It searches that customer's sales orders and invoices within the tolerance of the order total, and if nothing is in range it lists the nearest candidates instead of forcing a match. You get the two totals, the status and the difference with a verdict of matched, amount differs or no match. It will not compare across currencies, and nothing is changed.

Business outcome

---

Finance sees whether a web order and its Dynamics 365 Sales record agree, with near misses shown rather than forced into a match.
See Full Use Case

scenario

-

Someone opens a store order and then hunts through the ledger for its invoice. A wrong total or a missing invoice is usually only noticed at month end, when it is much harder to trace.

What popdock provides

--

Give a BigCommerce order id, and optionally a tolerance, and it reads the order and its lines, finds the Rillet customer by billing email, and looks for the invoice that carries the order id. If none does, it picks the closest total within 7 days and says the match was inferred. It reports total, currency, date, status and amount due side by side, and lists Rillet credit memos when the order has a refund. It refuses to pick between equally good invoices, does no currency conversion, and nothing is changed.

Business outcome

---

Finance sees whether each web order was invoiced correctly in Rillet, with inferred matches labelled and no invoice picked by guesswork.
See Full Use Case

scenario

-

A merchandiser checks a product in BigCommerce and then the matching item in Business Central, comparing price, cost and stock by hand. Drift between the two, such as a changed price or a blocked item still on sale, goes unnoticed until a customer orders it.

What popdock provides

--

Give a SKU, and optionally a Business Central company, and it looks up the product in BigCommerce, falling back to the product variant, and the item with the same number in Business Central. It tables name, price, cost, stock and blocked or visible status, marks each row as a match or a difference and gives the numeric gap. If either side is missing it says so instead of guessing, untracked BigCommerce inventory is shown as not comparable, and nothing is changed.

Business outcome

---

Merchandisers see price, cost and stock drift for one SKU in a single table, with missing records stated and untracked stock not flagged as an error.
See Full Use Case

scenario

-

The name, price, cost and stock of one SKU are compared by hand between the store and the ERP. That means looking in BigCommerce, then in Dynamics GP for the item, its price level and its quantities, and differences go unnoticed.

What popdock provides

--

Give a SKU, and optionally a Dynamics GP company, and it reads the BigCommerce product, falling back to the variant, and the Dynamics GP item with the same item number, its list price and its quantities. Available stock is on hand minus allocated, locations are summed and it says so, and if several price levels exist it names the one used. It tables each attribute as a match or a difference without saying which system is right. It stops when a record is missing on either side, and nothing is changed.

Business outcome

---

Operations gets every disagreement between the store and Dynamics GP for a SKU in one table, with no system declared the winner.
See Full Use Case

scenario

-

Someone compares BigCommerce customer exports with HubSpot contacts by hand, matching emails line by line. New buyers slip through unmatched, so they never reach a campaign, and records with different names or companies are not spotted.

What popdock provides

--

It reads BigCommerce customers created in the last 30 days, or the period you choose, up to a limit you set, and looks each one up in HubSpot by email, ignoring case. You get customers with no HubSpot contact, customers whose last name or company differs, and counts of checked, matched, missing and mismatched. Customers with no email are reported as unmatchable, duplicate HubSpot contacts are flagged, and it says when the limit was reached and the result may be incomplete. It only reads and nothing is changed.

Business outcome

---

Marketing sees which recent buyers are missing from HubSpot or recorded differently, with counts that show how many were checked.
See Full Use Case

scenario

-

Orders are checked against the ERP by hand from two exports, matching order numbers and totals line by line. Orders that never reached Intacct, or arrived with the wrong total, surface only at month end.

What popdock provides

--

It reads BigCommerce orders from the last 7 days, or the window you choose, optionally for one customer email, skipping cancelled, declined and incomplete orders. It matches each to an Intacct order entry document whose reference or customer PO number equals the order id, and compares totals, reporting gaps over 0.01. If the reference convention does not match, it says so instead of guessing another key. It reports orders as not comparable when currencies differ, says when more than 100 orders were capped, and nothing is changed.

Business outcome

---

Finance finds missing and mis-totalled orders within days instead of at month end, with unmatched Intacct documents listed too.
See Full Use Case

scenario

-

Sales quotes from the product list in the CRM while the store changes prices and SKUs. Nobody compares the two lists, so quotes go out at an old price or for a product that is no longer sold.

What popdock provides

--

It reads visible BigCommerce products, optionally filtered by a name fragment, up to 50, and the Nutshell products, then matches them on SKU ignoring case and spaces. You get three lists: in BigCommerce but not Nutshell, in Nutshell but not BigCommerce, and price mismatches with the difference, plus counts. Products with an empty SKU are listed separately because they cannot be matched, and prices are not compared when the Nutshell currency is not the store currency. It only reads and nothing is changed.

Business outcome

---

Operations sees which products are missing from either system and where prices have drifted, with currency mismatches noted rather than compared.
See Full Use Case

scenario

-

Newsletter sign-ups on the store and the people in Drip drift apart, and nobody compares them. Someone who signed up at checkout may never reach Drip, or may have unsubscribed there, so they are never emailed or are emailed against their wishes.

What popdock provides

--

It reads BigCommerce newsletter subscribers added in the last 90 days, or the period you choose, up to a limit you set, and looks each email up in Drip. You get three lists: in BigCommerce but not in Drip, in both but not active in Drip, such as unsubscribed, and in both and active, with counts and the email, name, source and date added for the first two. Emails are compared ignoring case and spaces, it never copies anyone between systems, and it stops when there are no subscribers.

Business outcome

---

Operations sees which store sign-ups are missing from Drip or unsubscribed there, so gaps can be fixed on purpose, not discovered by accident.
See Full Use Case

scenario

-

Newsletter sign-ups on the store and subscription status in HubSpot drift apart because nobody checks them against each other. A shopper may sign up at checkout and never become a HubSpot contact, or may have opted out in HubSpot already.

What popdock provides

--

It reads BigCommerce newsletter subscribers added in the last 30 days, or the period you choose, and looks each email up in HubSpot. When a contact exists, it reads that contact's subscription names and statuses. You get subscribers with no HubSpot contact, subscribers whose HubSpot status is not subscribed with the subscription name, and a count of those fully consistent. Emails are matched ignoring case, it never suggests re-subscribing someone who opted out in HubSpot, and nothing is changed.

Business outcome

---

Marketing sees which store sign-ups are missing or opted out in HubSpot, with opt-outs respected and never flagged for re-subscription.
See Full Use Case

scenario

-

The revenue Mailchimp credits to a campaign rarely agrees with what the store recorded. Checking it means listing the attributed customers, then searching BigCommerce for each one's orders, refunds and unpaid amounts, and nobody does that order by order.

What popdock provides

--

Give a campaign id, and optionally a start date, and it reads the campaign's revenue and the orders Mailchimp attributes to it. It then checks up to 25 of those customers in BigCommerce by billing email, summing order totals and refunds and noting unpaid orders. You get both sets of figures and the difference, customers who disagree by more than 1 percent, and customers Mailchimp credits with no store order. It says when a match was by billing email only, refuses to compare differing currencies, and says if only the first 25 were checked.

Business outcome

---

Finance sees how far Mailchimp's campaign revenue is from store orders and which customers explain the gap, with the 25 customer limit stated.
See Full Use Case

scenario

-

Before an account call, a rep checks the CRM for the organization, its people and deals, and then searches the store separately to learn what the account actually buys. People who buy but are not in the CRM, and contacts who never buy, are easy to miss.

What popdock provides

--

Give an organization name, and optionally a lookback period, and it finds the organization in Pipedrive, refusing to continue if the name matches more than one. It reads the organization's people and deals, finds each person in BigCommerce by email and also searches store customers by company name. It then pulls their orders for the period. You get the owner, open and won deals, store spend and order count, spend per person, store buyers who are not CRM people and CRM people who never bought. It only reads and nothing is changed.

Business outcome

---

Reps walk into an account call knowing whether CRM follow-up matches real buying, including buyers the CRM does not know about.
See Full Use Case

scenario

-

Gift certificate liability is checked by exporting the store's balances and comparing them with a balance sheet line by hand. The two drift apart unnoticed, and expired certificates that still carry a balance are rarely spotted.

What popdock provides

--

Give an as-of date, which defaults to today, and it sums the balances of active BigCommerce gift certificates, lists the five largest and notes any past their expiry date. It then searches the Rillet balance sheet for a matching line, trying gift, then deferred, then unearned, and shows which line it used. You get the store balance, the ledger liability and the difference. If no ledger line is found it says so and stops instead of assuming zero, certificates in different currencies are reported separately, and nothing is changed.

Business outcome

---

Finance sees whether the store's outstanding gift certificate balance agrees with the ledger liability, without a zero assumed when no line exists.
See Full Use Case

scenario

-

Big web orders arrive and nobody in sales knows whether the buyer is already in the pipeline. Finding out means pulling the order list, then searching Salesforce for each buyer's contact and open opportunities one at a time.

What popdock provides

--

Give a minimum order total and optionally a lookback period, which defaults to 14 days, and it finds the BigCommerce orders at or above that amount. It looks up each buyer's email in Salesforce for a contact and, when one exists, any open opportunity. You get a table per order with total, currency, payment status and the Salesforce result, then the orders with no contact as follow-ups. Orders with no billing email are listed as unmatchable, totals are never compared across currencies, and nothing is changed in either system.

Business outcome

---

Sales gets a follow-up list of large orders from buyers not yet in Salesforce, and sees which buyers already have an open deal.
See Full Use Case

scenario

-

Store managers export order lists and pivot them by hand to see counts, revenue and refunds by status. The totals drift by the time the sheet is shared, and the largest orders and refunded ones are easy to overlook in a long export.

What popdock provides

--

Ask for the last 7 days, or another period, optionally limited to one order status, and it reads the BigCommerce orders. It reports a headline of orders, revenue and refunds, a table by order status, a table by payment status, the discount total and the five largest orders. Orders with a refund are noted. It reads orders only and does not guess at causes. If nothing is found it says so, and if the record limit is hit it warns the figures may be incomplete and names the filter that would narrow them.

Business outcome

---

Store managers get current order counts, revenue and refunds by status without an export, with truncation stated instead of hidden.
See Full Use Case

scenario

-

An agent handling a case copies the customer's email into the store admin to find the order the customer is talking about. The case is in one system, the orders are in another, and picking the wrong order wastes time on the call.

What popdock provides

--

Give a Salesforce case number, and optionally a lookback period, and it reads the case subject, status and priority and the contact's email. It finds that person as a BigCommerce customer and lists their orders with date, status, payment status, total and refunded amount. It reads the items on the order that looks related to the subject and says which order seems relevant and why, or that none obviously is. It stops when the case has no contact or the match is ambiguous, and nothing is changed in either system.

Business outcome

---

Support sees the customer's recent orders next to the case and the most likely related order, without leaving the case to search the store.
See Full Use Case

scenario

-

To answer whether a customer has paid, support and collections staff open the store for the orders, then the ledger for the invoices and payments, then a spreadsheet to line them up. Orders with no obvious invoice, or overdue invoices, are easy to miss.

What popdock provides

--

Give a customer email, and optionally a lookback period, and it finds the BigCommerce customer and their orders, then the Rillet customer with payment terms, invoices, payments and credit memos. You get a customer header, tables of orders and invoices, total ordered against total invoiced against amount due, overdue invoices, and orders with no obvious invoice. Both systems' statuses are shown, and it never calls an order unpaid on the invoice side alone. It stops on an ambiguous email, shows the store side only if there is no Rillet record, and nothing is changed.

Business outcome

---

Support and collections answer whether a customer has paid from one view of orders, invoices and amounts due, with both statuses shown.
See Full Use Case

scenario

-

Someone chases an order from the storefront into the ERP by searching two admin screens. They cannot easily tell whether it was imported, invoiced or paid, or whether the lines and totals made the trip intact.

What popdock provides

--

Give a BigCommerce order id, and optionally a Business Central company, and it reads the order and its lines, then finds the Business Central sales document that holds the order id as its external document number. It compares line count, quantities and amounts, then looks for the posted invoice and its remaining amount. You get a short timeline from order to document to posted invoice, plus a list of discrepancies. Totals from both sides are shown before any gap is called an error, since tax or shipping can explain it. It only reads and nothing is changed.

Business outcome

---

Finance sees how far an order has progressed into Business Central and where it differs, without calling a tax or shipping gap an error.
See Full Use Case

scenario

-

Finding where a web order landed in the ERP, and whether the totals and lines agree, is a manual hunt across two systems. The order may have been keyed with a different reference, or with a changed quantity or price on one line.

What popdock provides

--

Give a BigCommerce order id, and optionally a Dynamics GP company, and it reads the order and its lines. It then finds the Dynamics GP sales document whose customer PO number holds the order id, using the closest amount if several match. It compares total and tax, then matches lines by SKU and item number, listing lines only on one side and lines whose quantity or price differs. It ends with a verdict of in step, differs or not in Dynamics GP, stops when a record is missing, and says the order may have been keyed with a different reference. Nothing is changed.

Business outcome

---

Finance sees whether a web order reached Dynamics GP and agrees with it, line by line, with a clear verdict.
See Full Use Case

scenario

-

Buyers see what sells in BigCommerce but see stock and open purchase orders in Dynamics GP, so spotting the best sellers that are about to run out means adding up order lines by hand and looking each SKU up in a second system. Refunded lines get counted by mistake, and a SKU runs dry before anyone raises a reorder.

What popdock provides

--

Name a GP company and, if you like, how many days to look back and how many top SKUs to check. It reads recent BigCommerce orders, adds up units sold per SKU without the refunded lines, then looks up on hand and on order stock and open purchase orders for each top SKU in that company only. You get days of cover and next promised date per SKU, with low cover and no order due flagged. SKUs that are not in PowerGP Online are listed separately, the number of orders read is capped and stated, and nothing is changed in either system.

Business outcome

---

Buyers see which best sellers will run out before supply arrives, in one read-only report, without cross-checking two systems.
See Full Use Case

scenario

-

Web prices are set in BigCommerce while costs sit in Dynamics GP, so margins are worked out in a spreadsheet after exporting both. Products with thin or negative margins go live, and a web price that drifted from the GP price list is only noticed by accident.

What popdock provides

--

Give a GP company, a minimum margin percent and, optionally, a brand. It reads the BigCommerce products, looks up the current cost and price list for each SKU in that company and calculates margin on the price the customer pays. You get a table of products under the threshold and a second table where the web price differs from the GP list price by more than 5 percent. Products with no GP item or a zero cost are skipped and counted, rows in another currency are flagged rather than compared, and nothing is changed in either system.

Business outcome

---

Thin margin products and web prices that drifted from the GP price list are found before customers buy them.
See Full Use Case

scenario

-

BigCommerce shows one stock level and Dynamics GP shows another, and comparing them SKU by SKU means opening two screens. The store oversells when its level is above what GP holds, and stock sits unlisted when GP holds more than the store shows.

What popdock provides

--

Name a GP company and, optionally, a SKU and a GP site. It reads BigCommerce inventory levels, including variant SKUs, then reads quantity on hand and on order from PowerGP Online for each SKU, summing sites when none is named. You get a table sorted by the largest difference, with oversell risk and stock not listed online flagged. Store only SKUs are listed and continued past, products where the store does not track inventory are noted, a run without a SKU covers the first 50 products and says so, and nothing is changed.

Business outcome

---

Oversell risk and unlisted stock show up in one sorted comparison instead of a manual check across two systems.
See Full Use Case

scenario

-

When a customer calls, their orders are in BigCommerce and their balance and overdue invoices are in Dynamics GP, so support opens both and pieces the account together. With no shared id, the wrong customer is easy to pick, and a high overdue balance goes unnoticed while the customer keeps ordering.

What popdock provides

--

Give a customer name or email and a GP company. It finds the BigCommerce customer, reads their recent orders with totals and refunds, then finds the PowerGP Online customer by name and reads balance due and open items with days past due. You get identity in both systems, order history, GP standing and one line on any concern. If several customers match on either side it lists them and stops, the GP match is stated as a match by name and not a confirmed identity, and nothing is changed.

Business outcome

---

Support sees orders and account standing together, with the identity caveat stated, and answers the customer in one pass.
See Full Use Case

scenario

-

The web catalog and the Dynamics GP item master drift apart, and comparing them means exporting both into spreadsheets and matching SKUs by eye. Products go live with no GP item, items never reach the store, and web prices fall below GP cost without anyone noticing.

What popdock provides

--

Name a GP company and, optionally, how many records to read per side. It reads BigCommerce products and PowerGP Online items, matches SKU to item number ignoring case and spaces, and retries a missing SKU once before calling it missing. You get three lists: store products with no GP item, GP items with no store product, and matches where cost differs or the web price is below GP cost, with counts. If no SKU matches it says the systems appear to use different identifiers and stops, capped reads are labelled as samples, and nothing is changed.

Business outcome

---

Missing items and below cost web prices surface in one reconciliation report instead of spreadsheet matching.
See Full Use Case

scenario

-

To confirm a web order reached Dynamics GP, finance searches sales documents by customer and date and hopes the PO field holds the order number. Totals and statuses are compared by eye, and nobody is sure whether the order was invoiced or paid.

What popdock provides

--

Give a BigCommerce order number and a GP company. It reads the order status, payment status, total and lines, then searches PowerGP Online sales documents from a week before the order for one whose customer PO equals the order number. For a match it compares amount and status and checks receivables for an invoice and whether it is paid. If the order number is not recorded in GP it says so and offers close candidates labelled unconfirmed, never as a match. It stops if the order is not found, and nothing is changed.

Business outcome

---

Finance sees whether a web order was entered, invoiced and paid in GP, with any difference in total stated.
See Full Use Case

scenario

-

Before a customer call, you open BigCommerce to read their details and orders, then search your task list for anything that mentions them. Putting the two pictures together by hand takes a while, and a refunded order or an open task is easy to miss.

What popdock provides

--

Give a customer email and it finds that customer in BigCommerce, stopping if nothing matches or if several do. It reads their orders over a lookback window, then searches TickTick for tasks by last name and by order number and reads the comments on each. A task is included only when it also mentions the email, full name or an order, and it says which one matched. You get a one-page brief with details, orders, totals, tasks and up to three observations. Nothing is written to either system.

Business outcome

---

You walk into the call with orders, refunds and open tasks in one brief, and no ambiguous customer match slips through.
See Full Use Case

scenario

-

To see which BigCommerce orders have a follow-up task, someone lists the orders by status and then searches the task app for each order number. Tasks that point at orders in a different status or an older window are just as easy to overlook.

What popdock provides

--

Give an order status and a lookback window, and it reads the matching BigCommerce orders. It then finds TickTick tasks titled with an order number and matches each order to a task by that number. You get counts for three groups, orders with a task, orders with no task and orphan tasks, plus tables of orders without a task, oldest first, and of orphan tasks. It only reports, and every write on both systems is ruled out.

Business outcome

---

You see which orders have no follow-up task and which tasks point at stale orders, without comparing two systems by hand.
See Full Use Case

scenario

-

Before a call, a rep searches the BigCommerce admin for a customer's orders, then searches Attio for the same person, company and deals. The two systems never quite line up, with different company names or a missing record on one side, and the preparation can take longer than the call.

What popdock provides

--

Give an email and optionally how many days of orders to include, and it finds the customer in BigCommerce and totals their orders, then finds the person in Attio with their company and deals. You get the store profile, order count, revenue and latest order beside the CRM person, company and deals, and a closing line on whether name and company agree. The email is compared ignoring case, it stops if more than one record matches, reports a missing match on either side instead of guessing, and changes nothing in either system.

Business outcome

---

A rep opens a call with store history and CRM context in one view, and every mismatch between the two systems is shown.
See Full Use Case

scenario

-

To check whether pipeline numbers match real revenue, someone exports Attio deals and BigCommerce orders for the same account and compares them by hand. Store customers have to be found by company field or by each contact's email, and deal values and order totals are different measures, which makes the comparison easy to get wrong.

What popdock provides

--

Name a company and optionally a lookback period, and it finds the company and its deals in Attio, then finds its BigCommerce customers by company field and by the email of each Attio contact, removing duplicates. It totals their orders and compares won deal value with store revenue, calling out open deals for companies already ordering and lost deals for companies that kept ordering. It shows how each customer was matched, flags currency differences instead of converting, stops if the company match is ambiguous, and changes nothing.

Business outcome

---

Finance sees pipeline value next to real store revenue for an account, with the matching method and any currency issues stated.
See Full Use Case

scenario

-

Large store orders can come from accounts that sales has no deal for. Spotting them means reading the BigCommerce order list, working out who each buyer is, including guest checkouts, and then searching Attio person by person and company by company.

What popdock provides

--

Give a minimum order total and a start date, and it lists the BigCommerce orders at or above that total, leaving out cancelled and refunded ones. It identifies each buyer, using the billing details for guest checkouts, then looks for the person in Attio by email, and for their company and deals. You get a table of orders with no deal, sorted by total, showing whether the buyer exists in Attio at all, and a second table of orders that do have a deal. It says when a match was by company name only, lists unidentifiable buyers as unattributed, and changes nothing.

Business outcome

---

Sales can follow up on large store orders from accounts with no deal, without searching the CRM name by name.
See Full Use Case

scenario

-

New store customers never reach the CRM, and finding the gap means exporting recent BigCommerce customers and checking each email in Attio by hand. Capital letters in emails and customers who checked out with no email make the comparison untidy, so the gaps go unnoticed.

What popdock provides

--

Give a start date and how many customers to check, and it lists the BigCommerce customers created since then and checks each email against Attio people. Matching is on email only, ignoring case, and never on name. You get a table of customers missing from Attio with store id, name, email, company and date created, a table of matches, and counts of checked, matched, missing and unmatchable. Customers with no email are reported separately, it tells you when the maximum was reached so there may be more, and nothing is changed.

Business outcome

---

You see which new store customers are missing from Attio, ready to add, with counts that show how far the check went.
See Full Use Case

scenario

-

When a customer asks what they ordered, what they were billed and what they still owe, an agent has to look in the store, then in the books, and line the two up by hand. Names and ids differ between systems, so it is easy to quote the wrong balance or miss a paid order with an unpaid invoice.

What popdock provides

--

Give a customer email and it finds that person in BigCommerce and in FreshBooks, then builds one view. You see their BigCommerce orders with dates, status and totals, next to their FreshBooks invoices, payments and the outstanding balance. If the email matches no one or several customers, it stops and lists them instead of guessing. If the two systems hold different names for the same email, it shows both and does not choose. Nothing is changed in BigCommerce or FreshBooks.

Business outcome

---

Support agents answer order and billing questions from one view, with mismatches called out and no records changed.
See Full Use Case

scenario

-

Product catalogues and item lists live in two places, so the same SKU can carry a different price or stock level in BigCommerce and FreshBooks. Nobody compares them line by line, and the difference only shows up when a sale or an invoice goes wrong. Nobody has time to compare them row by row.

What popdock provides

--

Optionally name a SKU, or let it read up to a set number of rows, and it compares BigCommerce products and variants with FreshBooks items by SKU. It reports SKUs whose price or stock differs, SKUs found only in FreshBooks and SKUs found only in BigCommerce. Items with no SKU are skipped and counted, and a SKU that appears twice on one side is listed as a duplicate rather than compared. Prices are compared only when they share a currency, and it notes that a FreshBooks unit cost is not necessarily a selling price. Nothing is changed in either system.

Business outcome

---

Price and stock gaps between BigCommerce and FreshBooks surface before a sale goes wrong, with no records edited.
See Full Use Case

scenario

-

Orders get paid in the store, but nobody checks the books to see whether an invoice was ever raised. Paid orders sit unbilled for weeks because spotting them means matching order totals and customer emails against the invoice list by hand. Revenue is earned but never billed.

What popdock provides

--

Give a start date, and optionally a payment status, and it reads the BigCommerce orders since then. For each billing email it checks FreshBooks for a client and for an invoice that matches the order, by purchase order number or by amount and currency. You get a table of unbilled orders showing order id, date, email and total, grouped by whether the customer already exists as a FreshBooks client, with a count and total value. Uncertain matches go to a separate needs review list, and nothing is created in either system.

Business outcome

---

Finance sees which paid orders still need an invoice, with doubtful matches kept apart and nothing created.
See Full Use Case

scenario

-

Someone exports BigCommerce customers and FreshBooks clients and compares email addresses in a spreadsheet. The two lists drift apart a little each week, and customers missing from the books or clients missing from the store go unnoticed. Missing records mean missed invoices.

What popdock provides

--

Give a start date and a row limit, and it reads recent BigCommerce customers and looks each email up in FreshBooks, then does the same in reverse for FreshBooks clients. You get matched pairs, customers missing in FreshBooks, clients missing in BigCommerce and customers skipped for having no email, with counts. Several clients on one email are reported as ambiguous with their ids instead of picking one, and if either system returns nothing it stops. Nothing is added or changed in BigCommerce or FreshBooks.

Business outcome

---

Teams see who is missing on each side in minutes, with ambiguous matches flagged and no records changed.
See Full Use Case

scenario

-

Orders are checked against invoices by eye, one customer at a time. Unbilled orders and invoices with the wrong amount or payment state only surface at month end, when they are harder to untangle. Fixing them then means digging back through weeks of orders.

What popdock provides

--

Give a date range and it reads the BigCommerce orders in that period, ignoring cancelled and incomplete ones and saying how many. It finds each customer in FreshBooks by email and matches an invoice by purchase order number, or by the same amount and currency. If two invoices fit equally well, it lists both and picks neither. Each order gets a verdict of matched, amount differs, payment state differs, no invoice or no client, with counts per verdict. Amounts are compared only in the same currency, and nothing is changed in either system.

Business outcome

---

Finance catches unbilled orders and invoice differences within the period, with ties listed and no records changed.
See Full Use Case

scenario

-

An agent answering a Freshdesk ticket has to leave the help desk, search BigCommerce for the requester by hand and scroll through their orders. With several recent orders it is easy to open the wrong one and answer about the wrong purchase.

What popdock provides

--

Name a Freshdesk ticket and it reads the requester, subject and status, then finds that customer in BigCommerce by email and lists their recent orders with the items bought. If the ticket mentions an order number, that order goes first. You see order date, status, payment status, totals, refunds and shipped items, plus a sentence on which order the ticket most likely concerns. It matches on email only, never on name, stops if the ticket has no email or no customer is found, and changes nothing in either system.

Business outcome

---

Agents see the right BigCommerce order beside the ticket in one answer, with no manual search and no guessed customer match.
See Full Use Case

scenario

-

To help a customer well, an agent needs to know what they bought and what they complained about. That means switching between the help desk and the store, looking up the same person in each and piecing the dates together, and a missed link means a refund or an order issue goes unnoticed.

What popdock provides

--

Give a customer's email and optionally a look-back period. It finds the customer in BigCommerce, or as a guest, and lists their orders and recent items, then finds the same person in Freshdesk with their tickets. You get a short customer header and one chronological timeline of orders and tickets, with up to three observations. Matching is on email only. If several customers match it stops, and if the emails differ it reports both. It is read-only.

Business outcome

---

Agents see a customer's orders and tickets on one timeline, matched by email, without switching between two systems.
See Full Use Case

scenario

-

High-value customers with unresolved support problems are not visible until they complain loudly. Finding them means listing the large recent orders in the store, then searching the help desk for each customer's tickets one at a time.

What popdock provides

--

Give a lookback in days, 30 by default, and a minimum order total, 500 by default. It finds BigCommerce orders at or above that total in the period, then looks up open Freshdesk tickets for each billing email. Customers with open tickets come first with their order IDs and totals and each ticket's priority, due date and escalation, followed by the customers with no open tickets listed by name. A customer with no tickets is treated as clear, and it stops and says so if no orders qualify. Nothing is changed in either system.

Business outcome

---

Leadership sees which big spenders have unresolved support problems, ranked first, so they can be handled before they escalate.
See Full Use Case

scenario

-

Support contacts in Freshdesk and shoppers in BigCommerce are kept by different teams and drift apart. Finding which contacts are not customers, which customers have no help desk record and whose phone or company differs usually means spreadsheets and a lot of lookups.

What popdock provides

--

Give a record limit and optionally a Freshdesk company, and it reads contacts from Freshdesk and customers from BigCommerce. It matches on lower case email and compares name, phone and company name. Before calling a Freshdesk contact missing from BigCommerce it looks the email up directly, and it says that a BigCommerce-only result from a limited read is only a candidate. Contacts with no email are counted separately. You get counts first, then up to 20 examples per group. Nothing is changed in either system.

Business outcome

---

You see how far the help desk and store customer lists have drifted, with confirmed gaps and examples, without spreadsheet work.
See Full Use Case

scenario

-

Low satisfaction scores sit in the help desk and refunds sit in the store, so the customers who are both unhappy and costly never show up together. Each team sees half the picture, and the expensive complaints go unnoticed.

What popdock provides

--

Set a highest rating and a lookback window, and it finds the Freshdesk satisfaction ratings at or below that level and the ticket and requester email behind each. For each email it checks BigCommerce for orders around that period, noting refunded amounts and cancelled, refunded or declined orders. The table shows email, rating, ticket, orders found and total refunded, then names the customers with both a low rating and a refund, largest first. Customers with no orders are listed as no orders found, not dropped. It is read-only on both systems.

Business outcome

---

You see which unhappy customers also cost you a refund, ranked by amount, from one read-only report across Freshdesk and BigCommerce.
See Full Use Case

scenario

-

Getting new BigCommerce newsletter signups into a HubSpot list means exporting subscribers, looking each email up in HubSpot, checking who is already on the list and adding the rest by hand. It is easy to add the wrong contact when an email matches twice, or to miss that someone has unsubscribed in HubSpot.

What popdock provides

--

Name the HubSpot list, and optionally how many days back to look, and it reads recent newsletter subscribers from BigCommerce and finds each one in HubSpot by email. Subscribers with no HubSpot contact are reported, not created, and emails that match several contacts are left out. It flags contacts HubSpot shows as unsubscribed, uses the list only if it is a manual list or plans to create it, and skips people already on it. Nothing is written until you confirm, BigCommerce is only read, nobody is subscribed, and each new member is checked on the list afterwards.

Business outcome

---

Recent BigCommerce newsletter signups reach the right HubSpot list in one pass, with unsubscribes flagged and no contacts invented.
See Full Use Case

scenario

-

Order follow-up tasks in HubSpot stay open after the BigCommerce order has been paid, shipped or completed, so the team keeps chasing orders that have already moved on. Checking means opening each order in BigCommerce and comparing its status by hand.

What popdock provides

--

Optionally give the task title text, and it reads open HubSpot follow-up tasks and takes the order id and the status recorded in each title. It looks each order up in BigCommerce and sorts tasks into done (now shipped or completed, or paid since it was awaiting payment), closed another way (cancelled, declined or refunded, left open for you) and not done, with days past due. Tasks with no readable or matching order are left alone. Nothing is completed until you confirm, only the task status changes, BigCommerce is only read, and each status is checked afterwards.

Business outcome

---

Order follow-up tasks close as orders move on, so the team only chases the orders that are really stuck.
See Full Use Case

scenario

-

When your catalog lives in BigCommerce, the HubSpot product library falls behind: new products are missing and prices and costs go stale. Comparing them means matching SKUs one by one and editing HubSpot by hand, and a sale price copied by mistake ends up on every quote.

What popdock provides

--

Optionally give a product name filter, and it reads BigCommerce products and matches each one to the HubSpot product library by SKU. Products with no SKU are listed and left out, and variant SKUs are not copied. It sorts products into create, update and skipped, showing before and after values for name, price and cost; name matches under a different SKU and duplicate SKUs are listed, not touched. It copies the regular price, not the sale price. Nothing is written until you confirm, BigCommerce is only read, and every product is read back afterwards.

Business outcome

---

The HubSpot product library matches BigCommerce by SKU, price and cost, with every change reviewed first.
See Full Use Case

scenario

-

Orders that sit in Awaiting Payment or another status for days are easy to miss in BigCommerce, and chasing them means finding each buyer in HubSpot and setting up a follow-up by hand. Without a check, the same order gets chased twice or a buyer is never contacted at all.

What popdock provides

--

Choose the order status and how many days old an order must be, and it reads the matching BigCommerce orders with their items. Each buyer is matched to one HubSpot contact by billing email, and orders with no email, no match or several matches are listed and left out. Orders that already have an open follow-up task are skipped. You see the table and nothing is written until you confirm, then each task is created on the contact and company, with higher priority for declined payments, and checked afterwards. BigCommerce is only read.

Business outcome

---

Every stuck BigCommerce order gets one follow-up task on the right HubSpot contact, so no order is forgotten or chased twice.
See Full Use Case

scenario

-

Checking whether a customer's details match in the shop and the books means opening BigCommerce, then Wave, and comparing name, phone and company by eye. Mismatches go unnoticed until an invoice or an order goes to the wrong person.

What popdock provides

--

Give the customer's email, and the company if you have more than one Wave business. It finds the customer in BigCommerce by email, then the same customer in Wave, and compares name, phone and company details, ignoring case, spacing and phone punctuation. You get a table of each field with the BigCommerce value, the Wave value and match or differ, plus the amount outstanding and overdue in Wave and the BigCommerce customer id. It stops and lists the matches if there are several, reports a one-sided record, and changes nothing in either system.

Business outcome

---

Mismatched customer details between the shop and the books are found in one question, with no changes made to either record.
See Full Use Case

scenario

-

Keeping the shop catalog and the books product list in step is a manual comparison. Missing items and price differences between BigCommerce and Wave linger because lining up two long lists by name and sku takes time nobody has.

What popdock provides

--

Optionally give part of a product name and the Wave company. It reads the active products in Wave and the BigCommerce catalog, and checks the BigCommerce store currency so prices are only compared when the currencies can be confirmed as the same. It matches by name ignoring case and extra spaces, and also when a Wave name contains a BigCommerce sku exactly. You get products only in Wave, only in BigCommerce and matched with different prices, with counts. If results are truncated it says the comparison is partial, and it changes nothing in either system.

Business outcome

---

Gaps and price differences between the shop and the books are found in one pass, with no changes made to either catalog.
See Full Use Case

scenario

-

Shop customers who never made it into the books are hard to spot, because it means comparing the BigCommerce customer list with the Wave customer list by hand. Invoices then get raised late, or not at all, for people who never reached Wave.

What popdock provides

--

Give a start date for new BigCommerce customers and optionally a Wave company. It reads the customers created since then, up to 200, and looks each email up in Wave. Customers with no match are listed with BigCommerce id, name, email and date created, followed by counts checked, matched and missing. It checks at most 40, the newest first, and says how many it did not check. Customers without an email are listed separately, truncation is called out and nothing is created in Wave.

Business outcome

---

Shop customers missing from Wave are found by email, with unchecked and email-less customers called out and nothing created.
See Full Use Case

scenario

-

Month-end matching of shop orders to invoices is usually done in spreadsheets. Orders without invoices, invoices with a different total and invoices with no order slip through, and cancelled orders and mixed currencies make the totals unreliable.

What popdock provides

--

Give a date range and optionally a Wave company. It reads BigCommerce orders and Wave invoices for the range, ignoring cancelled and incomplete orders and saying how many. Orders are matched by purchase order number equal to the order id, then by customer name and equal total, and a name only match is shown as a total mismatch. The report lists orders with no invoice, matched orders with different totals and the difference, and invoices with no order. Currencies are never added or compared, partial results are flagged and nothing is written.

Business outcome

---

Orders without invoices, wrong totals and orphan invoices are found for the period, with no currency mixing and nothing changed.
See Full Use Case

scenario

-

Finding out how much a customer buys and what they still owe means opening BigCommerce for the orders, then Wave for the invoices and balance, and totalling both by eye. If the shop sells in more than one currency it is easy to add amounts that should never be added.

What popdock provides

--

Give a customer email, how far back to look (365 days by default) and, if needed, the Wave company. It finds the customer in BigCommerce and stops if there is no match or several, then reads their orders. It finds the same customer in Wave and reads outstanding and overdue amounts and invoices. It reports order count, totals per currency, refunds, the last three orders and the unpaid invoices. Phone numbers and addresses are left out and nothing is changed in either system.

Business outcome

---

You see what a customer has bought and what they owe side by side, with currencies kept apart and no data changed.
See Full Use Case

scenario

-

Before a customer call, someone reads the customer record and recent orders in BigCommerce, then searches Todoist for related work. The two never line up, because Todoist has no customer field and the tasks only mention a name or an order number in their text.

What popdock provides

--

Give a customer email and, optionally, how many days of orders to look back, 90 by default. It finds the customer in BigCommerce and stops if there is no match or more than one. It lists their recent orders, then searches Todoist for open tasks that name the customer, their company or any of their five most recent orders. The brief shows how each task matched and marks name only matches as weak, then flags unpaid or refunded orders with no open task and tasks past due. It only reads and writes nothing to either system.

Business outcome

---

Walk into a customer call knowing their orders and the open Todoist work about them, with weak matches labeled and nothing changed.
See Full Use Case

scenario

-

After orders ship in BigCommerce, the matching Todoist tasks stay open because nobody cross checks the store. The task list fills with finished work, and a task that cites several orders is hard to judge by eye.

What popdock provides

--

Optionally give the shipped status name, Shipped by default, and how many days of orders to look at, 30 by default. It lists shipped BigCommerce orders in that window, then finds open Todoist tasks that cite them, matching order numbers only as whole numbers. A task that cites several orders qualifies only when every one has shipped. You see a table and name which to close, or say all. It closes only approved tasks, then reads each back to confirm it is completed, and reports closed, failed and skipped. It never deletes and never changes BigCommerce.

Business outcome

---

Todoist tasks for shipped BigCommerce orders are closed after you approve them and checked, with the store data left untouched.
See Full Use Case

scenario

-

When an order needs a follow-up, someone reads it in the BigCommerce admin and retypes the status, total and customer into a Todoist task. Details get dropped, and when two people react to the same order you end up with two tasks and no clear owner.

What popdock provides

--

Give an order number, a Todoist project and, if you like, a due date. It reads the order in BigCommerce, then checks Todoist for an open task that already cites that order and stops if one exists. It also stops if the project name matches none or several projects. You see the exact task, with status, customer, total, payment status and billing email, and nothing is created until you say yes. It then reads the stored task back. BigCommerce is never changed.

Business outcome

---

Each order gets one follow-up task with the right details, created only after you approve it, with no duplicates.
See Full Use Case

scenario

-

Orders stuck in a status such as Awaiting Fulfillment are checked against the team task list by hand. The ones nobody has taken on are only found when the customer complains, and a task that mentions part of an order number is easy to count by mistake.

What popdock provides

--

Give an order status (Awaiting Fulfillment by default) and how many days back to look (14 by default). It lists BigCommerce orders in that status and checks open Todoist tasks for each order id, counting a task only when the id appears as a whole number. It reports the orders with no task, with date, total, payment status and customer name, then the orders that do have tasks and the count of each. It stops if no orders match and shows the statuses it saw, and it warns when Todoist returns nothing at all. Nothing is created or changed.

Business outcome

---

You see which orders in a status have no owner in Todoist, so the untracked ones are picked up before customers chase them.
See Full Use Case

scenario

-

Low stock shows up in the BigCommerce admin, while restock work is planned in Todoist. Unless someone compares the two, a product can run out because no restock task was ever created, or because the task was written up and lost.

What popdock provides

--

Give a stock threshold, or let it use 5. It lists visible BigCommerce products at or below that level, skips products that do not track inventory, and searches open Todoist tasks for each product sku, using the name when there is no sku. You get a table of products with no task, lowest stock first, and a list of products already tracked with their due dates. Name-only matches are labelled as weak, the lookup is capped at the 25 lowest-stock products with the rest counted, and nothing is changed in either system.

Business outcome

---

Low-stock products with no task are listed lowest first, so restocking is raised before they sell out, with nothing changed in either system.
See Full Use Case

scenario

-

Finding which people on a shared project are also store customers means copying emails from Todoist into BigCommerce one at a time, then checking each customer's orders. It is slow, and a mistyped email gives a false answer.

What popdock provides

--

Name a Todoist project. It finds the project, stopping if it is ambiguous or missing, and lists its collaborators. For each email it looks up a BigCommerce customer by exact email, ignoring case, and for each match counts the orders and finds the most recent order date. You get a table with the collaborator, email, project role, matched customer id or not a customer, order count and last order date, plus totals checked, matched and not matched. It matches on email only, never name. Collaborators without an email are reported as no email, and if one email matches several customers it lists the ids and does not pick one. Nothing is changed.

Business outcome

---

Matched collaborators appear with customer id and order history, and the rest are counted, so you know who already buys. Nothing is changed.
See Full Use Case

scenario

-

To find out who is handling a BigCommerce order, someone looks the order up and then searches Todoist for its number. Tasks that cite it as order 1042 or #1042, or that sit in a comment rather than the title, are missed, and a longer number containing the digits gives false hits.

What popdock provides

--

Give the BigCommerce order id. It reads the order with its status, payment status, total, dates and product lines, and stops if the order does not exist. It searches open and completed Todoist tasks for the id, keeps a task only when the id appears as a whole number, and says how many look-alikes it discarded. It reads the comments on each matched task for what they say about the order. The report shows the order and a table of tasks with their latest comment, ending with how many tasks track the order. Nothing is changed in either system.

Business outcome

---

You see an order and every task that tracks it, open or done, without false matches from similar numbers.
See Full Use Case
No items found.

ready, go

Tools for BigCommerce

Start with ready-made MCP tools for the BigCommerce. Each one gives your AI client a single, clearly defined job: get invoices or journal entries, pull a file, or create and update records. Add a tool to your PopdockAI MCP server, choose the fields it returns and who can use it, and it's ready in Claude, ChatGPT or Microsoft Copilot. Nothing is exposed that you haven't switched on.

Tool Types

Name of tool
Description
get-data
bigcommerce-get-subscriber
Returns subscribers from BigCommerce, with filters for the fields that matter on this list. Read-only; needs a BigCommerce connection.
get-data
bigcommerce-get-store-info
Returns store info from BigCommerce, with filters for the fields that matter on this list. Read-only; needs a BigCommerce connection.
get-data
bigcommerce-get-site
Returns sites from BigCommerce, with filters for the fields that matter on this list. Read-only; needs a BigCommerce connection.
get-data
bigcommerce-get-shipping-zone
Returns shipping zones from BigCommerce, with filters for the fields that matter on this list. Read-only; needs a BigCommerce connection.
get-data
bigcommerce-get-product
Returns products from BigCommerce, with filters for the fields that matter on this list. Read-only; needs a BigCommerce connection.
get-data
bigcommerce-get-product-variant
Returns product variants from BigCommerce, with filters for the fields that matter on this list. Read-only; needs a BigCommerce connection.
get-data
bigcommerce-get-price-list
Returns price lists from BigCommerce, with filters for the fields that matter on this list. Read-only; needs a BigCommerce connection.
get-data
bigcommerce-get-page
Returns pages from BigCommerce, with filters for the fields that matter on this list. Read-only; needs a BigCommerce connection.

Ready to unlock your data?

‍

Start building tools that turn your business systems into AI superpowers

Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

Try PopdockAI Free
See Documentation