Your marketing team wants to launch three campaigns this quarter. Your developers have time for one. That gap can slow a growing online store. Campaign pages wait while other work takes priority.
BigCommerce Development Services and tools like Makeswift can ease that problem. Marketers can build pages themselves. Developers can spend more time on custom code, apps, and other work that needs their skills.
Makeswift is a visual page builder that BigCommerce bought in 2023. It gives merchants a way to build store pages without writing code. Think of it as a bridge between developers and the marketing team.
Developers build the main parts of the store. Marketing teams can then create and update pages on their own.
Makeswift works closely with BigCommerce Catalyst. Catalyst is a headless storefront built with Next.js and React. That sounds more technical than it needs to.
Catalyst separates what shoppers see from the systems behind the store. The front end is the part customers use. The back end stores products, orders, and other data.
Makeswift lets users edit the front end through a visual tool.
Here is what Makeswift can do:
One detail matters here. Catalyst has the deepest built-in link with Makeswift. Makeswift support for Stencil is still in beta.
If your store uses a Stencil theme, review the current support before planning a move. BigCommerce Headless Commerce can also help if you want more control over your store front end.
Developer delays can cost time and sales. A campaign may be ready, but the page is not. Seasonal offers can miss key dates. Product launches can lose steam.
Visual page builders help remove that wait. Marketing teams can build much of the page themselves. They do not need to turn every small change into a developer ticket.
That also cuts down on long review loops. Anyone who has heard "that is not quite what I meant" after a full sprint knows the pain.
Here is why this matters for e-commerce:
For growing BigCommerce stores, this is more than a handy feature. It gives each team a clearer job.
Marketing can manage content. Developers can handle the harder technical work. That is usually a better use of everyone's Tuesday afternoon.
Makeswift setup is fairly simple when you start with Catalyst. Here is the basic process.
Log into your BigCommerce control panel. Go to Channels and click "Create Channel." Choose "Catalyst."
Next, name the channel. You can also choose sample data if you want help learning the setup.
Pick your main language. BigCommerce then creates the new channel.
The One-Click Catalyst setup creates a preview store and a linked Makeswift site. BigCommerce says setup takes minutes.
Open Channel Manager in BigCommerce. Find the Catalyst channel you just created.
Click "Edit in Makeswift." Single sign-on opens the Makeswift editor.
You will see ready-made pages, page parts, and theme options. From there, you can start changing the design.
This step can trip up new users. You need two settings turned on.
First, open the Catalyst channel in BigCommerce. Turn on "Product Syncing to Makeswift."
Next, open the Makeswift site settings. Turn on "Routes."
These settings link your product catalog with Makeswift. Product changes in BigCommerce can then move into Makeswift through webhooks.
Product syncing is still in beta.
For One-Click Catalyst, BigCommerce lists these main permissions:
Local Catalyst work also needs access to create store-level API accounts.
Missing access can stop setup fast. Check your user role before you begin.
Once you open Makeswift, you can build and review pages from one visual editor.
"Build" lets you add and select page parts. "Navigate" lets you move through the page more like a shopper would.
Makeswift includes page parts that work well for online stores:
These parts give marketing teams a starting point. Developers can add custom parts when the store needs more.
Here is a simple process for a promo landing page:
The editor shows your changes as you work. Check the page on phone and tablet views before you publish.
That small check can save you from discovering a giant button on mobile after launch. We have all seen that movie.
Shared components can save a lot of repeat work.
Say your store has a free shipping banner. You could add that banner to each page by hand.
Or you can build it once as a shared component. Change it once, and the update can appear everywhere it is used.
Teams often use shared components for:
This also helps keep the store design consistent.
Makeswift supports live team editing. More than one person can work inside the editor at the same time.
You can see where other team members are working. Changes also save as people work.
That cuts down on version mix-ups. It also reduces those awkward "I thought you were finished" messages.
A nice-looking page still needs to be easy to find and use. SEO should be part of the build process.
Pay attention to these items on each page:
You do not need to force keywords into every field. Make the page clear first.
Large image files can slow down a page.
Before you upload an image:
Tools like TinyPNG can help shrink large files.
Strong landing pages often follow a few simple rules:
If you need help with store SEO, BigCommerce SEO Services can review the site and find areas to improve.
Makeswift handles page design. Your store will still need apps and other tools behind those pages.
The way those tools connect depends on what they do.
This is where developers can add more value.
Makeswift gives marketers ready-made page parts. Developers can also build custom React components for Catalyst.
For example, a store may need:
The developer builds that component once. Marketers can then use it on more pages.
The basic process is:
Marketers can then use that part without editing the code.
If your store uses NetSuite, Makeswift does not replace that connection.
Your BigCommerce NetSuite Integration still moves needed data between BigCommerce and NetSuite. Makeswift mainly controls what shoppers see.
For stores using the NetSuite Connector for BigCommerce, the main ERP link still works outside Makeswift.
The front end may still need testing during a move to Catalyst. That is especially true for apps that change what shoppers see or do.
Back-office tools can often keep working when a store moves to Catalyst.
The same is true for many API-based apps.
Storefront apps need more care. Some may need Catalyst-ready code or a new API setup.
Review your app list before moving. It is much easier to find a problem before launch than during checkout on launch day.
Most page builders promise easier page design. The useful question is how the tool fits your store and your team.
The best option still depends on your store.
A newer tool is not always the right tool. Sometimes the simple setup already does the job just fine.
Once your team knows the basics, a few habits can make Makeswift easier to manage.
Preview major page changes before publishing them.
Check phone, tablet, and desktop views. Click each link. Test forms and buttons.
Publishing can happen fast. A final review helps stop small mistakes from going live.
Catalyst is built with speed in mind. Poor page choices can still slow it down.
Keep these habits in mind:
A modern store framework helps. It cannot fix a page loaded with giant images and six video players.
You can connect Google Analytics through the Catalyst setup.
Other tracking tools can also be added based on your store needs.
Track visits, shopper paths, and sales actions. This helps you see which pages work and which ones need changes.
Makeswift supports scheduled publishing for accounts that have the feature enabled.
You can use it for planned sales, product launches, and campaign updates.
This can make launch days easier. Your team does not need someone waiting near the publish button at the exact launch time.
Set a few rules before the editor gets crowded.
Decide:
These rules do not need to be fancy.
They just need to stop five people from editing the same promo while nobody knows who owns it.
Makeswift can make page work easier. A strong online store still needs solid systems behind those pages.
As a BigCommerce Certified Partner, Anchor Group helps businesses build stores that work well with the rest of their systems.
Here is where we help:
Have a quick Makeswift or Catalyst question? The BigCommerce 30-minute fix gives you direct access to an expert.
We are Midwestern born and bred. We do not oversell. We do not overpromise.
If Makeswift is not right for your store, we will say so. That is simply how we work.
Catalyst includes built-in support for Makeswift. Your access can still depend on your account setup and enabled features. Some Makeswift tools may also have limits based on the account. Check your current BigCommerce and Makeswift access before planning a live rollout. This is the safest way to confirm which editing, publishing, and team features your store can use today.
Catalyst supports visual editing for both static and dynamic store pages. That includes landing pages, product areas, and other store content. Makeswift is not limited to simple campaign pages. The amount of control you have depends on how your Catalyst store is built. Developers can also add custom React parts that marketers can place and edit through the visual tool.
Makeswift works with Catalyst, which is built with Next.js and React. That gives developers a modern base for a fast store. Your content choices still matter a lot. Large images, heavy scripts, too many fonts, and auto-play videos can slow pages down. Compress files and test key pages after major edits. Page speed should be checked as part of normal store work.
You do not need code skills for basic page editing. Marketers can add text, images, buttons, products, and other page parts. They can also change layouts and publish approved content. Developers are still useful for custom React components and deeper Catalyst work. Many teams use this split. Developers build the harder parts once, while marketers reuse them across the site.
Yes, but the type of app matters. Back-office tools and API-based apps can often keep working outside the front end. Storefront apps may need extra work when you move to Catalyst. Some need Catalyst-ready code or a different API setup. Review key apps before launch. Test search, reviews, payments, analytics, and other shopper-facing tools before assuming they will work the same way.
Related Articles
Tagged with Training
