In brief
You’ll have a store that processes orders the same way every time, calculates shipping and tax the way you expect, and records revenue and conversions in GA4 so you can tell what actually drove sales.
I’ll start with a teardown of what you have, then map the safest path to a working cart, shipping, tax, and tracking. You’ll end up with a store you can sell through without guessing where orders or data go. If you’re ready, I’ll send a short kickoff checklist and book our first call.
I run this work by pulling the risky parts forward. I check checkout, shipping rules, tax behavior, and tracking before I touch design details, because those are the places that drop orders and break reporting. You’ll get clear decisions in writing as we go, plus a record of what changed and why.
A bit about me
I’m Megan Krolikowski, an ecommerce consultant. I got into this work the practical way: fixing stores that looked fine on the surface but failed at checkout, tracking, or product data once real customers started using them. Most of my weeks are a mix of migrations, rebuilds, and “why is this number wrong” debugging.
People hire me when they want fewer surprises. I’ll tell you when something is a quick fix and when it is a structural problem, like product data that can’t map cleanly to variants or tracking that was installed twice. I keep the work anchored to order flow and measurement, and I document decisions so you can run the store after launch.
Recent work
A few recent ecommerce store builds and rebuilds where the goal was simple: clean orders, correct data, and tracking you can use.
Portfolio
Shopify migration build. Moved a product catalog from a patched-together site into Shopify, cleaned variants, set up shipping rules, and carried redirects so search traffic kept landing on the right products after launch.
Checkout and tracking repair. Audited checkout settings, fixed payment and shipping edge cases, and rewired GA4 and GTM events so purchases, refunds, and key funnel steps matched what the platform recorded.
WooCommerce rebuild cleanup. Rebuilt theme configuration, normalized product attributes used for variants, and corrected tax and shipping settings that were producing inconsistent totals at checkout across different addresses.
“Checkout stopped breaking, and GA4 finally matched what we saw in orders.”
Owner-operator, a small product brand moving into a full store
How this runs
I keep the work predictable: I confirm decisions in plain language, I test changes where they can break orders, and you always know what I’m doing next and what I need from you.
1. Teardown and goals Days 1-3 I review your current store, checkout flow, shipping and tax rules, and tracking setup. You’ll get a written list of the high-risk breaks I see, plus a short set of decisions to make early, like platform direction and what has to stay the same for customers. 2. Platform and stack Week 1 I narrow the platform and app stack to a shortlist that fits your catalog shape and order volume, then I explain the tradeoffs in normal language. You pick the direction, and I map how product data, redirects, and tracking will carry over so the move is controlled. 3. Build and wire-up Weeks 2-4 I set up the theme and navigation, configure checkout and payments, and implement shipping and tax behavior. In parallel I clean product data for variants and imports. You review the store the way a customer uses it, and I adjust based on what you spot. 4. Launch and monthly care Ongoing I run launch checks on checkout, order confirmation, and tracking, then I stay involved month to month if you want ongoing support. Each month starts with a short list of priorities, like fixing funnel drop-offs, planning tests, or tightening shipping rules after real orders.
Pricing
Pick the option that matches where you are right now: a clean build, a migration with messy product data, or a build plus ongoing monthly care after launch. Prices are per month.
Priced items
Get started
If you want me to take this on, the next steps are simple and we can start as soon as the kickoff is booked.
1. Sign this proposal to reserve your build slot. 2. Pay the setup deposit invoice so I can start work. 3. Send your store logins and product export, then we’ll do the teardown call.
Signature
Fee summary
Payment
Ecommerce store build is billed 25% to start and 75% when the build is complete. Monthly care is invoiced at the start of each month. Every invoice is payable within 7 days.
Schedule. I’ll confirm the start date once the deposit is paid and I have what I need to begin. Timelines move when access, content, or product data shows up later than planned.
What I need from you. Before I can build and wire things up, I’ll need logins, product data, brand assets, and your shipping and tax rules. I’ll send a short checklist so nothing gets missed.
Changes to scope. If you decide to add categories, apps, tracking changes, or migration work that wasn’t in the original plan, I’ll write it up in plain language with the cost before I do it.
Reviews and sign off
You’ll get review points during theme setup, catalog import, and pre-launch checks. If feedback comes in as one consolidated list per review, I can keep the build moving without rework loops.
Launch responsibility. I’ll run a pre-launch checklist for checkout, payments, shipping, tax, and tracking. You’re the final approver to go live, and you’ll confirm the products, prices, and policies shown on the site.
Ownership. Once your invoice is paid, the store, theme configuration, tracking setup, and documentation I created for this ecommerce store build are yours. Any third-party apps, themes, or plugins stay under their own licenses.
Monthly care cancellation. Monthly care runs month to month. You can cancel before the next invoice date and I’ll stop work at the end of the paid month. I’ll hand over notes so you can keep running cleanly.
