After over a decade, WooCommerce finally introduced a native GTIN field, which seemed promising to me at the time. However, this seemingly straightforward feature has opened up more questions than it answered, leaving Woo sellers struggling to fully leverage this field. Here’s why.

WooCommerce’s GTIN Field: A Late Arrival

WooCommerce’s decision to introduce a dedicated GTIN field was long-awaited by users and developers – it was a pleasant surprise for me after using custom fields for over a decade. Until now, most shops I worked for had to rely on custom fields or third-party plugins to store GTINs (separate from SKUs). This native support should have, in theory, streamlined product data, improved SEO, and simplified integration with marketplaces.

However, this introduction revealed significant gaps. None of WooCommerce’s official plugins — like Google Product Feed, Facebook for WooCommerce, or other product import/export plugins — actually recognise this GTIN field. Woo’s product export doesn’t even support it. This oversight means shop owners are still forced to create workarounds, manually copying GTIN data into fields that can be read by other tools.

Why Google Needs a Crawlable GTIN

For businesses relying on Google Shopping as a sales channel, GTINs are more than just optional fields; they’re critical. Google uses GTINs to identify products accurately in its search index, allowing the platform to match identical products from multiple sellers and compare prices.

Google’s product feed specifications require GTINs to be included in a way they can easily crawl, such as in an exportable feed or directly on product pages. Without this, a shop’s product visibility suffers, leading to lower rankings and missed sales. Unfortunately, WooCommerce’s current GTIN implementation doesn’t meet these requirements.

A Workaround: Custom Fields and Plugins

For now, WooCommerce shop owners who need a GTIN in their product feeds are back to where they started—relying on custom fields or third-party plugins to get the job done. Many plugins designed for Google Product Feed generation still rely on custom GTIN fields, and without an update to these plugins, WooCommerce’s native GTIN support remains largely, and suspiciously, symbolic.

Developers and store owners are also turning to code customisations, creating ways to map WooCommerce’s GTIN field to Google’s feed requirements. This approach requires technical know-how, making it less than ideal for the average store owner.

What Needs to Change

For WooCommerce’s GTIN field to live up to its potential, support needs to be extended across WooCommerce’s official extensions. Specifically:

1. Google Product Feed: WooCommerce’s Google Product Feed plugin should automatically recognize and use the native GTIN field. This integration would allow for seamless compliance with Google’s requirements.
2. Product Feeds and Exports: Any product export features should make the GTIN field available for mapping to ensure GTINs are crawled by Google and other search engines.
3. Third-Party Plugins: Given the high usage of WooCommerce’s API by third-party plugins, WooCommerce should ensure that its GTIN field is exposed in a way that allows for straightforward integration by external developers.

What’s Next for WooCommerce Users?

Until WooCommerce bring their tools up to speed, store owners can continue to use custom fields and plugins as a stopgap. But if WooCommerce wants to remain in its position trusted position as a serious eCommerce platform for the long haul, updating these tools to natively support GTINs should be high on the agenda and future feature rollouts should be delayed until the basics have been covered.

For now, the GTIN debacle serves as a reminder that even small changes can have far-reaching impacts. And while the GTIN field’s release was a step forward, true support across WooCommerce’s ecosystem is needed to make this field a real asset for WooCommerce store owners.

How do I Import GTINs using WooCommerce’s default import?

The UPC is metadata that WooCommerce does not include in imports or exports. Simply create a sheet with Meta: _global_unique_id as a column and import using Woo’s default import tool. If you already have a list of products/SKUs, you can use VLOOKUP in sheets/Excel to match the UPCs.

How about Google for WooCommerce?

To ensure you can map your GTIN/ISBN to Google for WooCommerce, add the following snippet to your theme’s functions.php file:

add_filter('woocommerce_gla_attribute_mapping_sources_custom_attributes',
	function( $values ) {
		return array_merge( $values, ['_global_unique_id']);
	}
);

If you need a hand, feel free to reach out!

The post The WooCommerce GTIN change explained appeared first on The Web Co. Belfast.

D’fhéadfadh sé a bheith riachtanach luanna agus tagairtí a chur le postálacha WordPress do shuíomhanna gréasáin a láimhseálann ábhar acadúil nó tionscadail taighde. Sa bhlag seo, beidh tú ag foghlaim conas córas lua saincheaptha a chruthú i WordPress, le leideanna uirlisí agus liosta tagartha, ag baint úsáide as shortcodes agus cód PHP simplí.

Chruthaigh mé é seo le haghaidh tionscadal foinse oscailte ar a dtugtar The Énrí Ó Muirgheasa Project, which documents the author’s research on Irish song and culture, including “Dhá Chéad de Cheoltaibh Uladh” (Two Centuries of Ulster Song). Fágann an modh seo go bhfuil sé éasca luanna agus tagairtí a bhainistiú thar shuíomhanna WordPress, go háirithe le haghaidh taighde fairsing nó blaganna acadúla.

Céim 1: Cruthaigh gearrchód don lua

Tá gearrchód comhlua an-oiriúnach chun tagairtí a mharcáil ar fud d'inneachair, rud a fhágann go bhfuil sé éasca luanna a chur isteach agus a thaispeáint. Cruthóimid gearrchód dar teideal [cite] a úsáid cibé áit a dteastaíonn lua uainn.

// Citation Shortcode
function simplest_citations_cite_shortcode($atts, $content = null) {
    static $cite_count = 0;
    $cite_count++;

    // Store the citation content for tooltip and [citelist] shortcode
    global $citelist;
    $citelist[$cite_count] = $content;

    // Citation link with tooltip data
    $cite_link = '<sup><a href="#cite-' . $cite_count . '" id="cite-link-' . $cite_count . '" class="cite-tooltip" data-tooltip="' . esc_attr($content) . '">[' . $cite_count . ']</a></sup>';
    
    return $cite_link;
}
add_shortcode('cite', 'simplest_citations_cite_shortcode');

Cláraíonn an cód seo an "shortcode" [cite] , a choinníonn súil ar gach uimhir lua sa phost agus a shanntar leid uirlisí uathúil dó.

Sampla Úsáide

Cuir [cite]Téacs lua anseo[/cite] in aice leis an téacs ar mhaith leat tagairt a dhéanamh dó.

Céim 2: Cruthaigh Gearrchód Liosta Lua

Anois, cruthaímid "shortcode" [citelist] chun gach lua ag deireadh d'ábhar a aschur. Lúbfaidh sé seo trí gach lua a chruthófar agus taispeánfar iad i liosta ordaithe.

// Citation List Shortcode
function simplest_citations_citelist_shortcode() {
    global $citelist;
    $output = '<ol class="citation-list">';

    foreach ($citelist as $num => $citation) {
        $output .= '<li id="cite-' . $num . '">' . $citation . ' <a href="#cite-link-' . $num . '">[Back]</a></li>';
    }

    $output .= '</ol>';
    return $output;
}
add_shortcode('citelist', 'simplest_citations_citelist_shortcode');

Céim 3: Cuir an Liosta Lua i gceangal leis go huathoibríoch

Chun é seo a dhéanamh níos so-úsáidte, cuirfimid an liosta lua go huathoibríoch i ndiaidh an ábhair mura n-úsáidtear [citelist] go sainráite sa phostáil.

// Auto Append Citation List
function simplest_citations_append_citelist($content) {
    global $citelist;

    if (!empty($citelist) && strpos($content, '[citelist]') === false) {
        $content .= '<h3>Citations</h3>[citelist]';
    }

    return $content;
}
add_filter('the_content', 'simplest_citations_append_citelist');

Seiceálann an scagaire seo an bhfuil luanna i láthair agus mura n-úsáidtear [citelist] de láimh; má tá, cuireann sé ceannteideal “Citations” leis an liosta.

Céim 4: Cuir Tooltip CSS agus JavaScript leis

Ar mhaithe le UX níos fearr, stíleoimid na luanna le leid uirlisí a thaispeánfar nuair a ainlíonn úsáideoirí anuas orthu.

/* Tooltip CSS */
.cite-tooltip {
    position: relative;
    text-decoration: none;
    cursor: pointer;
	font-size: 0.8em;
}

.cite-tooltip::after {
    content: attr(data-tooltip);
    position: absolute;
    top: -80px;
    left: 50%;
    transform: translateX(-50%);
    width: max-content;
    max-width: 250px;
    background: rgba(0, 0, 0, 0.8);
    color: #fff;
    padding: 5px 10px;
    border-radius: 5px;
    font-size: 12px;
    display: none;
    z-index: 1000;
}

.cite-tooltip:hover::after {
    display: block;
}

Leideanna JavaScript (jQuery)

Cinntíonn an JavaScript seo go dtaispeánann an téacs leid uirlisí i gceart ar ainlíon.

(function($) {
    'use strict';

    $(document).ready(function() {
        const citeLinks = $('.cite-tooltip');

        citeLinks.each(function() {
            $(this).on('mouseenter', function() {
                const tooltip = $(this).data('tooltip');
                $(this).attr('title', tooltip);
            });

            $(this).on('mouseleave', function() {
                $(this).removeAttr('title');
            });
        });
    });

})(jQuery);

Íoslódáil agus Leathnaigh

Is pointe tosaigh maith é an struchtúr breiseán bunúsach seo. Is féidir leat é a íoslódáiltriail a bhaint as ar do shuíomh WordPress, agus é a shaincheapadh a thuilleadh de réir mar is gá. Má tá suim agat an breiseán seo a leathnú nó má tá aon aiseolas agat, ná bíodh drogall ort teagmháil a dhéanamh!

The post How to Add Custom Citations and References in WordPress (with Shortcode Tutorial and Free Plugin) appeared first on The Web Co. Belfast.

NHS Digital have released an updated Child BMI calculator. This is a small change that will be rolled out across the network and will result in no downtime. If you are a MyGP Pro subscriber, this Health Tools widget will be updated on Wednesday, 18th September 2024 at 10:00.

Medicines A-Z

NHS Digital have discontinued the current Medicines A-Z widget. This will be hidden across the MyGP Pro network. A new widget will be made available in the coming weeks and we will add this after release.

Referral programme

You can now refer colleagues directly from your surgery admin dashboard. Referrals will now automatically apply a 20% discount credit to your billing for 6 months.

Exciting updates and features coming next month – keep an eye on the roadmap in your dashboard 🙂

The post GP websites: Update to Child BMI Calculator appeared first on The Web Co. Belfast.

Navigating Successful Web Development Projects: Key Expectations and Avoiding Scope Creep

Getting started on a web development project is an exciting journey that holds great potential for transforming your business or personal brand and the main goal is almost always to increase sales or generate leads and bookings. Success hinges on clear communication, well-defined expectations and effective project management (more on that later).

This comprehensive (and sometimes messy) guide covers what you should expect from your web developer’s project scope before starting, how to avoid and manage scope creep during the project, and what should be completed before you pop open the Prosecco and sign the project as done.

So, without further ado, this is my developers’ guide for clients when building a new website.

Before the Project Begins: What to Expect from Your Web Developer’s Project Scope

1. Have a Detailed Project Description

I don’t begin putting a scope together until I have spend an hour talking through the project on Google Meets or Zoom. Face to face meetings, even online, can bring out much more information than a phonecall or a few emails with lists. A thorough project scope starts with a clear description of the project, including:

• Project Goals: Define the primary purpose of the website, whether it’s to sell products, generate leads or provide information.
• Target Audience: Identify who the website is aimed at to ensure the design and functionality meet their needs. If you’re working on an academic site we probably won’t use huge fonts with video backgrounds. Likewise if you’re a rockstar we might keep away from the pastels!
• Key Features and Functionality: Outline specific features needed, such as e-commerce capabilities, contact forms, or booking systems. An important part of our call is how each of these features will work. For example, a contact form could be used for user-submitted content, taking payments via Stripe or just a vanilla contact form.

2. Mark Down Your Deliverables

Your developer should provide a detailed list of deliverables. These can include:

• Design Deliverables: Mockups, wireframes, and final design files. This is not always necessary and a first draft can be provided based in inspiration you have found from other websites while researching.
• Development Deliverables: A list of additional software that has been scoped out that will meet your needs.
• Content Deliverables: A list of Text, images, and other media that developer will require. Consider using Dropbox, WeTransfer or Google Drive and always name images files descriptively.
• Documentation: From the beginning, the developer should begin compiling User guides and documentation for custom features. A finished document should be presented to you during go-live. I have found though that the vast majority of clients much prefer Loom videos.

3. Create a Solid Project Timeline

A realistic timeline is crucial for managing expectations:

• Milestones: Key dates for major deliverables, like first draft, design completion and testing phases.
• Deadlines: Specific deadlines for each project phase.
• Review Periods: Time allocated for you to review and provide feedback.

4. The Project’s Roles and Responsibilities

Clear roles and responsibilities prevent misunderstandings:

• Client Responsibilities: Providing content, feedback, and necessary access to systems. Not having logins to old websites for example, can delay the project by days or even weeks.
• Developer Responsibilities: Designing, developing, testing, and launching the website, plus ongoing support if agreed upon.

5. Define the Scope of Work

Defining the scope of work helps avoid scope creep:

• Inclusions: Tasks and functionalities included in the project.
• Exclusions: Clearly state what’s not included.
• Assumptions: Any assumptions made during planning that could impact the project.

6. Budget and Payment Terms

Transparency about costs and payment terms is essential:

• Total Project Cost: Detailed breakdown of costs, including design, development, and third-party services (particularly were WordPress plugins, Shopify apps or hardware such as POS for retail may be applicable).
• Payment Schedule: Milestone-based payment terms, such as initial deposit and final payment upon completion.
• Additional Costs: Potential extra costs for additional features or changes.

7. Testing and Quality Assurance for your new website

Quality assurance ensures the website functions correctly:

• Testing Phases: When and how testing will be conducted. I always test on dozens of real mobile and tablet devices in top browsers.
• Bug Fixes: Handling and timeframe for fixing identified issues. You will always be informed of any delay in case of unexpected bug fixes.

8. Website Maintenance and Support after launch

Post-launch support is crucial for ongoing success:

• Warranty Period: Period during which issues will be fixed free of charge. At The Web Co., this is standard at three months.
• Ongoing Maintenance: Options for updates, backups, and security checks.
• Support Availability: Developer’s availability for support and response times. We have our own dedicated support system which you will have access to.

Understanding and Avoiding Scope Creep

What is Scope Creep?

Scope creep is very common in the web development industry. This usually happens when the project scope expands beyond its original objectives due to additional features or changes introduced without corresponding adjustments to the timeline, budget, or resources. This can lead to significant delays, increased costs, and frustration for both parties. At The Web Co., we use a fantastic project management system to keep everything on track – you will also have live access to our Monday board.

The Main Causes of Scope Creep

Scope creep can be caused by:

• Unclear Initial Requirements: Vague project goals and deliverables.
  Our initial and post-kick-off call will avoid this.
• Poor Communication: Miscommunication or lack of communication.
  At The Web Co., we’re a bit different to move agencies and I (Robert) have worked with a few. I will schedule a 30-45 minute call each week, but you can still call us at any time with questions. I have found that the more issues I am asked to clarify with a client, the better is it to tweak my approach.
• Stakeholder Influence: Additional inputs or changes requested by stakeholders.

How to Avoid Scope Creep 😱

1. Clearly Define the Project Scope

Start with a well-defined project scope. Some call be a scope fanatic because I am meticulous and for a number of years my main job was working with other agencies re-working their scopes to get products back on track. One agency had my number saved as the firefighter – a role I love 🧑‍🚒 . So, how to define a scope clearly:

• Detailed Project Description: Clearly outline goals, objectives, and deliverables.
• Specific Requirements: Document all functionalities and design elements.
• Inclusions and Exclusions: State what’s included and excluded.

2. Effective Communication is key

Maintain regular and transparent communication:

• Regular Updates: Have a weekly call, with a few short ones in between.
• Feedback Mechanism: Establish a clear process for feedback. Each developer uses different tools, but at The Web Co., we’re huge fans of Bugherd.
• Documentation: Keep detailed records of communications and decisions.

3. Implement a Change Control Process

Manage changes systematically:

• Change Requests: Require formal change requests.
• Impact Assessment: Assess the impact of changes (some new functionality may affect existing functionality)
• Approval Process: Ensure changes are approved by both parties.

4. Set Realistic Expectations

Manage expectations from the start:

• Realistic Timelines: Develop realistic timelines.
• Flexible Yet Firm: Your developer will be flexible to minor changes but firm on significant deviations. Large changes, particularly where software is concerned can always be added to a mini-project post-go-live.
• Milestones: Break the project into manageable milestones.

5. Prioritise Features and Requirements

Focus on essential features first:

• Must-Have vs. Nice-to-Have: Categorise features accordingly.
• Minimum Viable Product (MVP): Aim for an MVP with core features before building out the rest of the project’s functionality.

6. Document Everything

Ensure comprehensive documentation:

• Project Scope Document: Keep it updated and signed off by both sides.
• Change Log: Maintain a log of all changes.
• Meeting Minutes: Document key points and decisions.

7. Collaborative Approach within the Client’s Team

Foster a collaborative environment:

• Involve Stakeholders: Engage stakeholders in planning and reviews.
• Regular Reviews: Conduct regular reviews to gather feedback.
• Problem-Solving Mindset: Approach challenges with a problem-solving mindset.

Before Signing Off: Ensuring Project Completion

1. Finalised Design Implementation

Ensure the final design matches the approved mockups and is fully responsive.

At The Web Co., this will always be the case but we have seen many cases over the years where mobile and tablet responsiveness has not been tested or corrected.

• Design Alignment: Matches approved mockups and wireframes (taking into account agreed changes along the way).
• Responsive Design: Works on all devices.
• Brand Consistency: Aligns with your brand’s guidelines.

2. Functional Features

Verify that all features and functionalities are operational:

• Core Features: E-commerce capabilities, contact forms, etc.
• Interactive Elements: Sliders, animations, interactive menus.
• Third-Party Integrations: Functional integrations with external services.

We will walk through each step together. This will also be on a regularly backed up staging website so do not be afraid to test is alone or with colleagues.

3. Content Population

Ensure the website is populated with final content:

• Text: Correct and error-free text.
• Images and Videos: Properly placed and optimised media. We will ensure media is served in next-generation format as long as they are provided in a large enough size to compress while remaining sharp.
• SEO Elements: Meta titles, descriptions, and keywords in place.

4. The developer must carry out Thorough Testing and QA

Comprehensive testing ensures a smooth launch:

• Cross-Browser Testing: Functions across all major browsers.
• Device Testing: Tested on multiple devices.
• Performance Testing: Loads quickly and performs well.
• Functionality Testing: All features work properly.
• Security Testing: Ensured site security.

You should always be given a report on this prior to considering signing off on a project.

5. Bug Fixes and Revisions

Address all issues identified during testing:

• Bug Resolution: All reported bugs fixed.
• Client Feedback: Revisions based on feedback given and completed.

6. User Training and Documentation

Receive necessary training and documentation:

• User Training: Sessions or tutorials on using and maintaining the site.
• Documentation: Guides and troubleshooting tips for custom features. I always create ‘How To’ videos in a private folder for each area of your website.

7. SEO and Analytics Setup

Prepare your site for search engines and tracking:

• SEO Optimisation: On-page SEO elements optimised.
• Analytics Setup: Tracking tools set up to monitor traffic (such as Google Analytics, Hotjar and Klaviyo)

8. Backup and Launch Preparation

The developer must ensure backups and launch readiness:

• Backups: Full backups to prevent data loss.
• Launch Plan: Detailed plan for a smooth launch to be signed off on.

9. Post-Launch Support

Understand the level of post-launch support:

• Support Availability: Immediate post-launch support period.
• Maintenance Agreement: Ongoing maintenance and support options.

Conclusion

Successfully navigating a web development project requires clear expectations, thorough planning, and effective communication. By understanding what to expect from your web developer’s project scope, being aware of scope creep and how to prevent it, and ensuring all necessary tasks are completed before signing off, you can achieve a successful project launch.

Following this developers guide for clients when building a new website will help set the stage for a smooth and productive web development experience, benefiting both clients and developers alike.

So remember:

1. Don’t sign off on a scope until you are sure it completed your new website’s needs
2. Ensure you receive a full QA and security report
3. A go-live plan should always be provided to you and agreed upon
4. Once the site is live, ensure speed optimisations are checked

I hope this has been helpful to you as a reader (both client and developer). If you have any questions, please don’t hesitate to send me an email. Do you have your own developers guide for clients when building a new website? If so, please share them with me.

Have a great day,
Robert @ The Web Co.

The post A Web Developer’s guide for clients building their first website project with a new developer appeared first on The Web Co. Belfast.

Scéim Tacaíochta Gnó

Tá Foras na Gaeilge i ndiaidh a Scéim Tacaíochta Gnó a rolladh amach arís! Cuidíonn an tionscnamh iontach seo le gnólachtaí beaga ar fud an oileáin le costaisí chomharthaíochta, pacáistiú agus láithreáin ghréasáin. Is féidir na sonraí iomlána a léamh ar shuíomh ghréasáin an Fhorais.

Seirbhís dhátheangach

Ag The Web Co., táimid bródúil as a bheith go hiomlán dátheangach agus tá bheimid sásta cabhrú le d’iarratas.

Má tá suíomh gréasáin úr de dhíth ar do ghnó, ná bíodh drogall ort teagmháil a dhéanamh linn – tiocfaidh druid leis an scéim seo nuair a bheidh an buiséad ídithe.

Cé nach bhfuil speisialtóireacht againn i ndearadh priontála, táimid thar a bheith sásta tú a threorú chuig dearthóirí priontála gairmiúla, dátheangacha.

Thig leat teagmháil a dhéanamh linn ar na sonraí thíos:
hello@thewebco.ie / 028 7192 2577 / 07908484175

The post Foras na Gaeilge open Business Support Scheme 2024 appeared first on The Web Co. Belfast.

We have built many websites where toggling taxes has been a big requirement and we have re-coded it in different ways over the years. Now, we’d like to introduce the Woo Customer Tax Toggle plugin!

Streamline tax control on your WooCommerce store by allowing users to toggle taxes seamlessly via navigation, a widget, shortcode, or a handy floating button.

With only 30 lines of CSS code, this plugin will not interfere with your current theme, customizer or WooCommerce color scheme. You can also override colours and change the ‘Display tax?’ text in each of the four locations.

This solution ensures a user-friendly interface while giving you complete control of your customers’ shopping experience.

Where can I add a tax toggle button?

This plugin will allow trade customers to toggle taxes on your website anywhere you like:

• Turn tax display on or off in your WP navigation menu
• Add a shortcode to toggle taxes
• Enable the floating tax toggle button
• Add a tax display widget to your widgetized areas

Shop Managers have complete design control to match their store brand. Check out our demo!

How do I get the Woo Tax Toggle plugin?

This was for sale – but a free version will be available at the end of April 2026 after some maintenance.

The post Woo Customer Tax Toggle appeared first on The Web Co. Belfast.

Hello fellow eCommerce enthusiasts! I have often been asked why I recommend one eCommerce solution over the other. The truth is there is no one-size-fits-all solution. Today, I’m sharing my own insights into why WooCommerce might just be the a better fit than Shopify for your eCom build. With nearly two decades of experience under my belt, I’ve seen it all in the eCommerce world, and I’m here to share some thoughts that might just make you reconsider your platform of choice. So, grab a cuppa and let’s get into it!

“Shopify is so cool!”

Absolutely, no arguments there! Shopify definitely has its merits, and it’s a platform we’ve worked with extensively, accounting for about a quarter of The Web Co.’s projects. However, WooCommerce takes the cake for us, with a whopping 40% of our workload. And there’s good reason for it!

Shopify shines for larger catalogs, seamless inventory management and team delegation – there’s no doubt about that. But when it comes to flexibility, affordability, and catering to the diverse needs of smaller businesses, WooCommerce steals the show.

So, when should I not use Shopify?

Shopify is costly

Let’s talk pounds and pence. Shopify’s pricing can be a bit steep, especially for smaller ventures like the bookshop I’ll use as an example. These businesses already juggle hefty overheads, and Shopify’s costs can sometimes tip the scales too far. Plus, without careful planning, unexpected expenses can crop up faster than you can say “online checkout”. More about scoping later.

We’re working on a large project – a bookshop with over 3,000 titles that requires synching between their online store and physical shop in Belfast. The first-year costs came to just under £5,000, including Shopify’s POS hardware, which didn’t include integration with marketing channels.

Most online shops are run by small business who can’t afford Shopify Plus, which starts at an eye-watereing £2,000 per month. This leaves shops at the mercy of apps which may not fulfil the project brief.

Scope your Shipping

Shipping woes? Let’s address those. Shopify’s shipping setup works like a charm if your products all fit into neat, uniform packages. But for businesses like our Belfast bookshop, with its varied mix of items in all shapes and sizes, WooCommerce’s flexibility wins out every time.

Many countries, including the UK, have national shipping services that don’t yet support volumetric shipping. Therefor shops need to have up to date shipping rates. If using Royal Mail, product weight and dimensions are collectively taken into account to calculate your shipping cost.

Shopify doesn’t have product dimensions as a product setting unless you create custom metafields. Shopify is US-centric without much taken into account for smaller country concerns.

Why not build a Shopify shipping app?

Sure, building a custom app for Shopify might seem like a tempting option. But let’s be real – it’s a commitment. Constant updates, tweaks, and adjustments can quickly turn into a headache, especially when dealing with ever-changing variables like shipping rates – not to mention ever-changing shipping zones.

So, what’s the solution? Enter WooCommerce plugins! After some thorough testing, we found gems like the Royal Mail Price Calculator from WP Ruby, which streamlined our shipping process and cut down on unnecessary complexities. We went from 8 zones down to one.

Shopify’s support offering

Now, let’s talk support. Shopify’s got a solid team backing it up, no doubt about it. Application developers are responsive and engaged. Where Shopify have been found wanting is their unresponsive sales support. This can be frustrating when purchasing on behalf of a client, especially where taxes are concerned.

But with WooCommerce, you’ve got the power of an open-source community at your fingertips. Need help? Just reach out, and chances are someone’s been there, done that, and can lend a hand.

What about WooCommerce POS?

Here’s the scoop – while Shopify POS is a smooth operator, WooCommerce’s options are a bit lacking. But fear not! With Square POS stepping in as the perfect sidekick, syncing stock and managing orders becomes a breeze.

Using Square alongside WooCommerce, start-up costs fell by 60% including POS hardware.

Developer tip: Square recommend setting Square as the inventory of record when selling both online and offline. The opposite is, in fact, most effective.

The Importance of Scoping

Before we wrap up, let’s touch on a crucial aspect of any eCommerce project – scoping. A well-documented plan is your roadmap to success, protecting you from scope creep and unexpected charges down the line. Whether you’re diving into WooCommerce or any other platform, take the time to outline your needs, test your assumptions, and ensure everyone’s on the same page from day one.

Your technical scope should always be your roadmap and cover all eventualities. When we are hired by external agencies to re-scope, get an eCommerce build back on schedule or to (frankly) put out fires, the issue is almost always down to ineffective or no technical scoping.

Make your finished scope a part of the contract with your client and use it as your step-by-step building guide.

What should I take away from this?

In a nutshell, Shopify’s fantastic, but it’s not always the best fit for every scenario. When it comes to versatility, affordability, and catering to the unique needs of smaller businesses, WooCommerce steals the spotlight. So, whether you’re shipping out books, mugs, or the latest gadgets, remember – there’s a platform out there that’s perfect for you.

If you’ve got thoughts, questions, or just want to chat eCommerce, I’m all ears! Drop me a line, and let’s keep the conversation going.

Stay tuned for the next installment of our series, where we’ll dive into why Shopify might just be the bee’s knees for certain ventures. Sign up below, and let’s keep exploring the wonderful world of eCommerce together!

The post When you should choose WooCommerce over Shopify appeared first on The Web Co. Belfast.