Start with the enquiry your team needs to act on
A Shopify-to-HubSpot integration for a business that sells through conversations should start with a question: what must the sales team know to give this buyer a useful first reply? The answer determines what the form asks, what HubSpot records and who follows up. Choose the integration method after those decisions.
That distinction mattered on the Royal Labs project. Royal Labs manufactures personal care products for other brands. The old Shopify site presented the company like a consumer shop, even though a prospective customer needed to understand its manufacturing capabilities and discuss a project. The new site was built on a custom Shopify theme, with a multi-step project enquiry form that sends submissions to HubSpot.
The published case study records enquiries after launch. It does not isolate the form’s effect from the redesign or report a measured conversion lift. The useful lesson is the change in buying path: a visitor can move from researching what the manufacturer can make to describing a project the team can follow up on.
Choose fields by working backward from the first reply
Give a salesperson a typical enquiry and ask them to write the reply they would send. What do they have to ask before they can do anything useful? If the answer is always product category, target volume and intended launch date, those are good candidates for the form. If the team only occasionally needs packaging specifications, save that question for a later conversation or show it only when relevant.
For an illustrative manufacturer, an initial project brief might capture company name, work email, the type of product being considered and a rough production range. A buyer who is exploring options may know the category but have no confirmed quantity. Offer an honest “still deciding” option if the team can handle those enquiries. A required number otherwise invites a guess that looks more certain in the CRM than it really is.
Separate three kinds of information during design. Contact details describe the person. Company details describe the organisation. A project brief describes this particular request. A buyer might come back six months later with a second project. Updating their contact record should not erase the earlier brief or make the sales team mistake two projects for one.
Use multiple steps when the questions have a natural order
A short contact form often works best on one screen. A longer form benefits from steps when later questions depend on earlier answers. Asking the buyer what they want to manufacture can determine which details matter next. Grouping unrelated fields into separate screens merely adds clicks.
Write the labels for the person outside your company. “Which product are you planning?” is easier to answer than an internal pipeline classification. Use ranges when an exact number is unlikely. On a phone, check that the visitor can go back without losing their answers, identify the field that needs attention and reach the submit button with the keyboard open.
Plan what happens when a request fails. If a timeout occurs after the visitor submits, the browser may not know whether HubSpot received the data. A second click can produce another submission. Decide how the team will distinguish a retry from a second project, and make the success message reflect the acknowledgement your system actually has. A successful screen after client-side validation alone does not prove the lead arrived.
Make the CRM handoff explicit
Before development, agree on a field map with the people who use HubSpot. For each question, record where the value lands, which formats are allowed and whether a blank answer can replace an existing value. Define who should see the resulting enquiry and what they should do next. HubSpot offers documented form submission interfaces with fields and optional submission context. The payload alone does not decide your sales routing or record ownership.
Walk through a returning customer with an existing record. Their current enquiry should reach the right team even if their email is already in the system. Then walk through a new buyer using a different email from the same organisation. Should it go to the same owner, or should someone review the association first? Those are business rules. Letting incidental CRM defaults settle them can make the first response slow or inconsistent.
Decide separately which details you need to respond to an enquiry and which data you collect for attribution or marketing. Ask the people responsible for your privacy process to review that distinction and the wording of any choices you offer. The first sales reply should not depend on capturing every attribution field.
Pick the simplest integration that supports the journey
An embedded HubSpot form may be enough when the fields are straightforward and your team already maintains that form in HubSpot. It gives the team one place to manage the questions. Test its rendering, validation and accessibility in the Shopify theme before committing to it.
A custom Shopify form is worth considering when the buying path needs conditional questions, tighter control over the interaction or a better fit with a custom theme. The extra control comes with responsibility for field mapping, validation and error states. Keep any credentials required by your chosen integration out of browser code. If your handoff needs privileged CRM operations, use an appropriate server-side path.
A broader connector can make sense when your business also needs order or customer synchronisation. A project enquiry can be a separate requirement. Start by describing the events you need, the system responsible for each record and the consequence if a sync is delayed. That gives you a clearer comparison than choosing an app because both logos appear in its listing.
Accept the work with a sales-side test
Ask the person who will receive the lead to sit in on acceptance. In an agreed test setup, submit a new enquiry, one with optional fields blank and one for an existing contact. Inspect what arrived, who can see it and whether the submission has enough context for a reply. Test a rejected submission and an interrupted connection. Recheck the form after a theme change so the team knows how to catch a regression.
After launch, look beyond the number of form submissions. How many reached the CRM with usable information? How many reached the correct person? How many received a reply within the team’s own target? These checks separate a weak offer or low-quality traffic from a form that loses enquiries after someone has already decided to contact you.
Frequently asked questions
Can Shopify send project enquiries directly to HubSpot?
Yes. A Shopify page can embed a HubSpot form or use a custom enquiry form connected through a supported submission method. The right choice depends on your fields, theme and routing needs.
Does connecting an enquiry form also sync orders?
A form handoff and an order sync are separate flows. Specify and test each one independently if the business needs both.
What should happen if an existing contact submits again?
Decide how the new request is associated with the contact and how previous project details are preserved. Include that case in acceptance so the team can see the actual outcome.
How do we know the integration works?
Follow a test enquiry from the page to the CRM and through the first sales handoff. Verify field values, ownership and the failure path alongside the success screen.