Getting More Out of commonsku: Connecting It to Your CRM and Pipeline

commonsku runs the job. A former promo rep on how to connect it to your pipeline and client relationships without double entry or a data migration, what commonsku already connects to, and where SIPS fits.

Has this ever happened to you? A client calls asking where their hoodies are, and you've got commonsku open in one tab, a pipeline spreadsheet in another, and a sticky note on your monitor that says "follow up re: reorder??" with two question marks, because past you wasn't sure either.

So was I. I ran my desk on commonsku, and the job side was never the mess. The order was right there. The mess was everything around it: who I'd promised to call back, which clients had gone quiet, what was sitting in my pipeline before a single estimate existed. I kept that in my head, and my head has a smaller memory than my laptop.

This post is about connecting commonsku to the rest of your sales life so you stop being the bridge. Some of it costs nothing. Some of it is software I built. I'll flag which is which.

commonsku runs the job. Let it.

commonsku describes itself as CRM plus order management for promo, and the job is where it lives: presentation, estimate, sales order, purchase order, proof, invoice, with the supplier working inside the same flow. That's the backbone a lot of shops are built on, and nothing in this post asks you to move off it.

The question worth asking is how the order details get from commonsku into the places you manage the rest of the relationship. Your pipeline review. Your follow-up list. The note that says this client always reorders onboarding kits in September.

If those live somewhere else, somebody is carrying the data across by hand. Usually that somebody is you.

What commonsku already connects to

Start here, because it's free and most shops never look.

commonsku's integrations page lists product search pulling from ESP, SAGE and DistributorCentral, so you can build presentations without leaving the platform. It lists QuickBooks Online and Xero on the accounting side. It also lists Zapier, HubSpot, Mailchimp, ShipStation, Shopify and Stripe, among others.

That's a real list. If your shop is running commonsku with none of those turned on, you're probably retyping something you don't have to. Open the integrations page, open your own account settings, and check what's available on your plan before you buy anything from anybody. Me included.

The boundary: I'm describing what commonsku publishes about its own integrations. What's switched on for your account depends on your plan and your setup, so confirm it with commonsku directly.

The Enterprise API, for the shops that have it

commonsku lists API access and webhooks on its Enterprise plan. If you're on Enterprise and you've got a developer or an integrations person, that's the most direct way to wire commonsku into anything you want. Use it. It's built for exactly that.

If you're not on Enterprise, or you are but nobody on your team writes code, you've still got options. That's the next section.

Where SIPS fits

Here's the disclosure. I built SIPS, short for Stout Intel Promotional Software. It's a promo-focused CRM built to manage the client's whole sales life: the relationship, the pipeline before a job exists, and the follow-ups after it ships. It works with commonsku and for commonsku users. It doesn't do commonsku's job.

The way it connects is the part I'm proudest of, because it asks nothing of commonsku. You already send clients public share links for presentations, estimates and invoices. SIPS reads those the same way your client's browser does. Paste one and the client, contact, line items, images, SKUs, quantities, cost, sell, margin per line, decoration detail, artwork, in-hands date and ship-to all land at once as a deal.

That's the whole point. No double entry. No data migration. Nothing to export, map or clean up first.

A few things I had to get right before I trusted it:

One job stays one job. The estimate, the sales order and the invoice for the same job carry the same job number. SIPS matches on it exactly, so all three land on one record instead of three cards claiming triple revenue. That was my CRM three weeks into building it, and I'd built it.

Stages only move forward. Paste an old estimate after the invoice already landed and it can't drag a closed job back to quoting.

It works on any plan. Essentials, Advanced or Enterprise. No login, no stored credential, nothing to configure on commonsku's side.

The boundary: SIPS reads share links you've actually shared. If a link was never sent, it can't see it. When commonsku changes the layout of a share page, the parser breaks, loudly, and the job shows an error instead of importing a wrong number. The fix is usually a small update to the parsing rules. It also isn't accounting, inventory or ERP. It's the sales side, and I'm not going to pretend it's more than that.

If you want the full mechanism, I wrote up how reading share links actually works. If you'd rather see it than read about it, paste one of your own share links here. Nothing is stored. It's your client's data and it's none of my business.

What to do this afternoon, without buying anything

You can run this on your own setup today, and you don't need my software to do it.

Open your last ten jobs in commonsku. For each one, write down every other place you typed any part of that job. The CRM, the pay sheet, the reporting spreadsheet, the client portal, an email to the warehouse. Count the retypes.

Then go through commonsku's integrations list and cross off every retype an existing integration already covers. Whatever's left is your actual problem, and now it has a number on it.

If what's left is mostly the sales side, the pipeline and the follow-ups, that's the piece SIPS was built for. If what's left is accounting, look at the QuickBooks Online or Xero connection first. Either way you'll know more than any software roundup was going to tell you.

If you run something else alongside commonsku

A lot of shops pair commonsku with other tools, and each pairing has its own handoff. I wrote separate guides for the common ones, same rules: what each tool is built around, where the handoff happens, and how to tighten it.

• Using ESP and commonsku together
• Using SAGE and commonsku together
• Using DistributorCentral and commonsku together
• OrderMyGear and commonsku: group stores and the job behind them
• Antera and commonsku: where each one fits
• Facilisgroup (Syncore) and commonsku: what each one asks you to sign up for

And if you're earlier than all of this, still working out whether you need a CRM at all, start with the best CRM for a promotional products company is probably not a CRM.

Pick one this week

Wire up what commonsku already offers, build on the Enterprise API if you're there, or paste a share link into SIPS and watch the job land. I don't much care which one you pick. I care that you stop typing the same 400 polos into four systems, because I did that for a year and nobody gave me a medal.

Stout Intel is independent and not affiliated with or endorsed by commonsku.