logo link37 agencia marketing digital

Why an ecommerce partner search is a different search

Most advice on choosing a HubSpot Solutions Partner is written for B2B companies closing a handful of deals a month, where the CRM is mainly where salespeople log calls. If you sell online, your reality is different: thousands of transactions, a store platform that already holds the commercial truth, payments that may settle days after checkout, and an ERP issuing the invoices.

So the criteria change. Three things decide whether an ecommerce HubSpot project works: how the store integrates with HubSpot, how the data is modelled once it lands there, and whether the partner has shipped the lifecycle campaigns that make that data pay for itself. Badges and logo walls are secondary. What follows is about choosing the partner, not configuring the CRM.

Integration architecture: the first thing to interrogate

Every ecommerce HubSpot project starts with one decision: how does Shopify, WooCommerce or Magento talk to HubSpot? There are three honest answers, and a good partner tells you which fits before you ask. A weak partner defaults to whichever they already know.

Make each candidate justify their recommendation against your order volume and catalogue: what happens when the sync fails overnight, how duplicates are prevented when the same person checks out as a guest twice, and whether historical orders are backfilled.

How ecommerce data should be modelled in HubSpot

Integration moves records; modelling decides whether they are usable. This is where ecommerce portals quietly fail: orders arrive, nobody can segment on them, and the team still exports to a spreadsheet. Ask the partner to whiteboard the model live. A competent answer covers:

• Products and line items. Whether the catalogue syncs into the product library, and how variants, bundles and discounts appear at line-item level. Without line items you cannot segment by what someone bought.
• Where orders live. Deals in a dedicated pipeline is the common pattern; a custom object often fits subscriptions, returns or split shipments better. There is no right answer, only a right justification.
• Contact-level aggregates. Lifetime value, average order value, order count, first and last order date, days since last purchase, dominant category, each with a refresh mechanism.
• RFM or an equivalent. Recency, frequency and monetary value turned into addressable segments: new, loyal, at risk, lapsed, high value. And if part of your revenue is wholesale, orders must associate to companies, not only contacts.

A useful probe: ask how they would list customers who bought category A twice in 180 days, never used a discount code, and have not opened an email in 90 days. A vague answer means a vague model.

The use cases that separate strong partners from weak ones

Anyone can describe an abandoned cart email. The difference is in the detail, and in whether the partner says when not to build something in HubSpot.

Abandoned cart and abandoned browse

Ask where the cart event comes from, how fast it reaches HubSpot, and how the sequence suppresses people who bought meanwhile. Ask whether the store's own recovery flow would do it cheaper — a partner who never recommends the tool they are not selling is optimising for the invoice.

Post-purchase, winback and segmentation

Replenishment timed to the real product cycle rather than a generic 30 days, which needs product-level data. A winback threshold derived from your real purchase interval, not a round number. And segments built on purchase behaviour rather than email engagement: discount-dependent, full-price and single-category buyers deserve different treatment.

Revenue attribution

Short buying windows, overlapping channels and last-touch flattering paid search break the classic B2B model. Ask which attribution model they would configure, what it cannot prove, and how it reconciles with your store and ad platform numbers. Anyone promising perfect attribution has not done this at scale. See also our overview of marketing automation in HubSpot.

Payments, invoicing and the ERP: the underestimated part

Payment methods change the automation logic. With Multibanco references, an order can be created at checkout and paid two days later, or never. If workflows trigger on order creation rather than payment confirmation, you will thank customers for purchases they never completed and chase carts already paid. MB WAY behaves differently again. Ask how they model order state versus payment state.

Invoicing is not HubSpot's job. Certified invoicing software and SAF-T PT reporting to the AT belong in your billing stack or ERP. HubSpot reflects commercial reality; it is not the system of record for fiscal documents.

The ERP is often the real integration. PHC, Primavera, Sage and SAP are common here, and stock, returns, credit notes and customer master data usually live there. Ask which they have integrated, in which direction data flowed, and who resolved conflicts when ERP and store disagreed. The answer should include a story, not a diagram.

Consent and GDPR in ecommerce lists

Ecommerce databases carry a specific risk: it is easy to treat everyone who ever bought as a marketing contact. Under the GDPR, with the CNPD as supervisory authority in Portugal, a purchase is not automatically consent to receive campaigns. A partner who knows ecommerce raises these unprompted:

• Separating transactional messages (order confirmation, shipping, invoice) from marketing ones, with different legal bases and suppression rules.
• Using subscription types so a customer can stop promotional email without losing delivery notifications.
• How consent is captured at checkout, passed through the integration, and stored with timestamp and source.
• What happens to historical buyer lists imported at go-live, and how an erasure request is executed across store, CRM and ERP rather than only in HubSpot.

If consent is left as a checkbox at the end of the project, you inherit a list you cannot safely use.

Ten technical questions to ask on the first call

Use these verbatim. You are testing whether they have built ecommerce, not whether they can talk about it.

1. Which integration approach would you recommend for our platform and volume, and why not the other two?
2. Where do orders live in your model — deals, custom objects or both — and what does that decision cost us later?
3. How do you sync line items, and how do variants and bundles appear in a list or report?
4. Which contact-level ecommerce properties do you create as standard, and how are they refreshed?
5. How do you handle guest checkout and the same person buying under two email addresses?
6. How do you distinguish order created from payment confirmed for deferred methods such as Multibanco?
7. Which ERPs have you integrated with HubSpot, and what broke the first time?
8. How do you backfill historical orders, and what is the impact on workflow enrolment and email sending?
9. How do you separate transactional and marketing consent, and where is proof of consent stored?
10. What monitoring sits on the integration, and who is responsible when it fails after go-live?

Then ask for a sanitised screenshot of a portal they built, and to speak to the consultant who would run your project, not the person selling it.

A scorecard for comparing shortlisted partners

Score each shortlisted partner from 1 to 5 below. The point is not the arithmetic; it is comparing on evidence rather than on how the call felt.

Deliberately absent: agency size. A four-person team that has connected Shopify to HubSpot twenty times beats a large agency on its first store.

Contract details worth fixing before you sign

Onboarding. Onboarding is mandatory on HubSpot Professional and Enterprise unless you buy through a certified Solutions Partner delivering an equivalent onboarding. If that is your route, get it in writing that the partner's commitment replaces HubSpot's mandatory fee, and compare offers on scope rather than headline cost. Our note on how Marketing Hub Professional onboarding is structured shows what one should contain.

Ownership and exit. Who owns the integration code, the middleware scenarios and the documentation if you change partner? Insist middleware runs on your subscription, not theirs.

Tier and certification. The programme has four tiers (Gold, Platinum, Diamond, Elite) and every tiered partner must hold a valid Solutions Partner Certification, re-examined every 25 months. Tier reflects volume of business with HubSpot; it says nothing about whether they have ever connected a store.

FAQ

Do I need a HubSpot partner if my store platform already sends emails?

Not always. If your whole lifecycle fits inside the store's native tools and there is nothing else to reconcile, HubSpot adds cost without adding much. The case strengthens with several data sources, a service team, or B2B and retail revenue in one business.

Should I choose a partner who works only with ecommerce?

Specialisation helps, but the better test is whether they have shipped your combination: store platform, ERP, payment methods. Broad HubSpot depth plus three comparable builds usually beats a specialist who has never touched your ERP.

How long should an ecommerce HubSpot implementation take?

A native app connection with standard lifecycle flows takes weeks; a custom ERP integration with backfill and a redesigned data model takes months. Be suspicious of any timeline quoted before anyone has seen your order data.

Can one partner handle the store and HubSpot?

Sometimes, and it removes a coordination layer. Link37 works on both sides, Shopify development and HubSpot implementation, which helps when the fix belongs in the storefront rather than the CRM. Verify both capabilities are staffed, not subcontracted.

Talk to Link37

Link37 is a HubSpot Platinum Solutions Partner based in Lisbon, working across Portugal, Spain and the UK. We implement HubSpot for ecommerce businesses and also build on Shopify, so integration decisions are made with both sides in view.

If you are comparing partners and want a second opinion on integration approach, data model or scope, get in touch and we will go through your setup.