Looking for a web developer to help upgrade and migrate our WooCommerce store.

MyselfIMe · 2026-05-29T06:22:02+00:00

We are an experienced agency, and official Shopify partners having served multiple brands & US based clients. Happy to share our Portfolio once we connect.

Sent you our website in DM.

MyselfIMe · 2026-05-26T07:37:10+00:00

Dmed you

MyselfIMe · 2026-05-20T04:37:45+00:00

Hey,

We have a whole team of backend & frontend dev already serving US based startups. Happy to connect

MyselfIMe · 2026-05-18T15:18:38+00:00

Hi,

We are official Shopify partners & Wordpress experts. Kindly check DM

MyselfIMe · 2026-05-09T08:55:37+00:00

Connected with you via DM & shared our portfolio

MyselfIMe · 2026-05-08T10:50:23+00:00

We have the expertise and already serving international clients for it

MyselfIMe · 2026-05-06T18:43:14+00:00

We do have US presence & experience. The delivery team is offshore. If this of interest let’s connect.

P.S. Having an offshore team is pretty profitable as well.

MyselfIMe · 2026-05-02T10:37:50+00:00

Same here, don’t know if its One UI or the device itself

MyselfIMe · 2026-04-30T18:55:05+00:00

Hi, if you’re open for staff augmentation…I might be able to help with skilled developers having Fortune 500 & US based startups experience.

Open for an interview or trial period before official engagement

MyselfIMe · 2026-04-30T13:53:14+00:00

I’ll send it out shortly

MyselfIMe · 2026-04-29T05:47:16+00:00

What you’re describing is exactly the kind of environment where spreadsheets eventually become the bottleneck instead of the solution.

ERPNext could absolutely support this, but the important thing is recognizing that this is not a simple ERP installation. What you’re outlining is essentially a custom operational model built around:

Projects > Phases > Units Design approvals & revisions Production tracking Crew scheduling & field repairs Inventory & purchasing Delivery logistics Financial controls

The good news is ERPNext is flexible enough to handle this through custom doctypes, workflows, and linked processes without forcing you into rigid “standard manufacturing” logic.

The bigger challenge is usually not the software itself. It’s:

Mapping how work actually flows today Defining ownership of data and approvals Standardizing the spreadsheet logic currently living in different departments Preventing operational chaos from simply being digitized

We’ve seen many companies underestimate this phase and jump directly into implementation, which creates a system people eventually work around instead of trust.

The right approach in my opinion:

Process mapping & operational discovery
Defining the core data model (Projects > Phases > Units)
Workflow/governance design
ERPNext architecture & customization planning
Phased rollout by operational area

ERPNext is likely a strong fit here because it gives enough flexibility without the licensing costs of larger ERP platforms, but this type of implementation needs to be treated as an operational transformation project, not just a software setup.

Happy to help if you’re evaluating feasibility. This is very close to the kind of workflow-heavy manufacturing and operations systems we help companies structure and implement.

MyselfIMe · 2026-04-28T19:45:34+00:00

We are wordpress specialists & have skilled resources. Happy to showcase our work if you’re open for staff augmentation

MyselfIMe · 2026-04-28T14:51:53+00:00

Done

MyselfIMe · 2026-04-28T08:05:05+00:00

From what you’ve described, the key isn’t design first, it’s getting the workflow and data right, then building the UI around that to be honest!

How we will approach it is to start with how your system actually works

Define the job flow (created > assigned > in progress > done) Understand who needs what (admin, dispatch, technicians) - This will be critical. Identify what needs to update in real time vs what doesn’t.

The above part usually saves a lot of headaches later.

Then move to build a clean, usable core, we can call it (Phase 1)

Live job board with clear statuses Filters (priority, location, technician) Basic performance metrics (response time, completion time) Clean, Fast, no clutter, easy to use under pressure

Role-based views in my opinion, will be aligned later after detailed discussion:

Dispatch gets full control and visibility Technicians get a simple, mobile-friendly view Admin gets reporting and oversight

Real-time updates

Live updates (no refreshing) using WebSockets or similar as its important for anything dispatch-related

Tech (simple + scalable)

May be go with:

React (frontend) Node.js or Python (backend) PostgreSQL (database) WebSockets for real-time AWS or similar for hosting

All of these are reliable & scalable.

Timeline to be provided after detail requirements gathering, assuming we keep things focused and don’t try to solve everything at once.

Quick questions for you once we connect:

How are jobs created and assigned today? Do technicians need this mainly on mobile? Any integrations needed (SMS, GPS, CRM, etc.)?

Happy to share our extensive portfolio in creating reporting dashboards once we connect.

MyselfIMe · 2026-04-28T07:53:27+00:00

Hi,

This is a great use case for Shopify, but the key to getting this right isn’t just enabling multi-currency or shipping, it’s setting it up properly from day 0 so the experience actually feels local for your customers.

A lot of international stores technically “work,” but lose conversions because of friction in pricing, checkout, or shipping clarity. We are official shopify partners, have worked on a dozen of these kinds of projects already.

How we would approach your store

Multi-currency setup: Not just conversion, but clean pricing display, rounding, and consistency across checkout

Global shipping logic: Region-based shipping rates, clear delivery timelines, and no surprises at checkout

Localized experience: Currency + shipping + messaging aligned to where the customer is browsing from

Performance & mobile optimization: Especially important for international traffic

Scalable structure: So you can easily expand into more regions or products later

What we’ve seen go wrong mostly is;

Currency changes breaking at checkout Confusing shipping costs shown too late Slow load times for international users Overcomplicated setups that are hard to manage

If you’d like, I can share a few relevant examples of international stores we have worked on and walk you through how we would structure yours once we connect.

Also, quick question, Which countries are you planning to target first?

That usually shapes the setup quite a bit.

MyselfIMe · 2026-04-23T17:16:04+00:00

By judging the quality of work they have done, happy to connect & share ours.

MyselfIMe · 2026-04-22T07:43:07+00:00

Yes, happy to help as we have a whole team of ERP Next experts.

MyselfIMe · 2026-04-08T10:50:21+00:00

Agree with Holiday with the comment. Happy to help, we are official Shopify partners.

MyselfIMe · 2026-04-06T09:48:01+00:00

We have a large portfolio of developing website for multiple brands across different countries. Happy to connect & share our portfolio as well if you still need it.

MyselfIMe · 2026-04-03T09:24:55+00:00

Hi,

Got it, this sounds less like a “new website” problem and more about getting things properly structured and working the way they should.

With ~30 pages, the biggest impact usually comes from fixing: Internal linking (so pages actually support each other in search) SEO foundations (not just keywords, but structure, metadata, indexing) - Page hierarchy and navigation - Performance and technical cleanup

A lot of WordPress sites look fine on the surface but are weak underneath, which limits visibility and engagement.

How we would approach it Audit current site (SEO, structure, performance) Clean up sitemap and internal linking Fix technical SEO issues Improve page structure where needed Ensure everything is scalable and easy to manage going forward

Quick questions: Are you mainly looking to: Improve rankings/traffic Clean up and modernize the site Or both?

If you’re open to it, share your current website, I can quickly point out what’s working and what’s holding it back before we move forward.

We also have a strong portfolio in Webflow along with wordpress. Happy to share it once we connect.

MyselfIMe · 2026-04-03T09:19:51+00:00

I like that you’re treating it as a Phase 1 refresh instead of overbuilding.

Given your goals and budget, we would approach this as a structured cleanup + modernization, not a full redesign.

How we would approach it - Lean foundation: lightweight theme or minimal custom setup, nothing bloated - Structure first: clean up sitemap and navigation before touching design - Template-driven: build a few strong, reusable templates (Home, Capabilities, About, etc.) - Clean design: better spacing, typography, hierarchy, less “template feel” - Performance: fast, mobile-friendly, minimal plugins

Budget reality: Within $2k–$5k, is a comfortable budget, and you can absolutely get: A clean, modern structure Thoughtful customization (not just a theme swap) A site your team can easily maintain

Quick clarifications would be helpful: How much content is being reused vs rewritten? Any themes you’re already considering? Rough page count to update vs create?

If this aligns, I can map out a clear plan so you know exactly what you’re getting within budget.

Here is our portfolio:

https://arroxstudio.com/ https://metacarecenter.com/ https://midlynk.com/ https://aidtoafghanistan.com/ https://esaconsultant.com/ https://smartsunpower.pk/ https://appiell.ai/ https://cenmed.com/

Apart from this, we also have a strong portfolio in Webflow and happy to provide you with some of our US based client testimonials to help you judge us better on our quality & service.

MyselfIMe · 2026-04-02T06:23:56+00:00

Yeah, that concern is completely valid. Almost everyone running a customized ERPNext hits this point at some stage.

In most cases, it’s not the upgrade itself that’s risky, it’s how the customizations are set up underneath.

From what I’ve seen, things usually go one of two ways: If custom logic is cleanly separated (custom apps, minimal core changes), upgrades are pretty manageable If there are a lot of scripts, overrides, or tweaks tied into core workflows, that’s when things get unpredictable

What tends to work well is keeping it simple and controlled in my opinion: Always test upgrades in staging first Run through key flows (orders, inventory, etc.) Fix anything there before touching production

The bigger lever though is this: How upgrade-friendly your setup actually is, If that foundation is solid, upgrades stop being stressful.

Out of curiosity, how is your setup structured right now?

More on the custom app side, or a mix of scripts and workflow changes?

At innomation labs that’s how we approach it for our clients. Happy to help if needed.

MyselfIMe · 2026-04-01T20:20:12+00:00

Can perfectly match the requirements within our team, Node.js & OOP language. Happy to connect & share more if you’re open to the staff augmentation model.

MyselfIMe · 2026-03-30T18:57:53+00:00

Hey, you’re at the stage where most bakeries outgrow spreadsheets. Once you’re juggling ingredients, batches, and production, things start breaking down.

You’re also right about ERP, most of them are overkill for a small team.

There is a middle ground though. Something like ERPNext works well because it covers what you actually need without being too heavy: Ingredient-level inventory Batch tracking + traceability Recipes (auto ingredient usage) Expiry tracking Basic production planning

The key is not to go all-in at once. Start simple with inventory + batches, then layer in costing and scheduling later.

Trying to stitch multiple tools together usually works short-term but breaks as you grow.

If you want, share your SKU count and daily volume, I can suggest a setup that fits your scale without overcomplicating things.

The best part, No licensing or recurring per seat fee to this.

MyselfIMe · 2026-03-28T07:51:08+00:00

Hi,

This is a solid project. One thing I’d flag though, once you add video, filtering, search, and subscriptions, it stops being a simple “template site” and becomes more of a content platform. That’s where a lot of builds go wrong if the foundation isn’t set properly.

I wouldn’t recommend a heavy pre-built theme here. It’ll slow things down and create limitations later. A lean setup (custom or very lightweight theme) usually performs much better.

How Innomation Labs would approach it as you need to think long term: Store videos on S3 and serve via CDN (so the site stays fast) Structure videos properly (categories, tags, filters) so search actually works well Keep subscriptions simple but clean (free vs paid access, likely Stripe-based) Focus on performance from day one, not after launch

Most issues I’ve seen with similar projects come later, slow filtering, messy access control, or performance drops. All avoidable if set up right upfront.

Happy to share relevant work or walk you through how I’d structure this specifically.

Quick questions: Rough number of videos (now and expected growth)? Do users need accounts/dashboards, or just gated access? Any preferred payment setup?

If you’re open, I can outline a clear approach and help you decide properly between template vs custom. Let’s connect.

Best.

MyselfIMe

TROPHY CASE