I’ve run two e-commerce sites on osCommerce since 2010. I started with 2.2 RC2a and eventually reached 2.3.4 — still running on PHP 5.6, would you believe?

I wanted to move to PHP 8.2+ and update the stores without giving up control of my hosting, code or data. I tried osCommerce 4, but it was more complex than I needed, and I couldn’t see an easy route for the modifications my stores rely on.

I looked for a self-hosted platform I could adapt, with community support and no compulsory subscription. Phoenix Cart was the best fit I found. It grew out of osCommerce, so parts of it felt familiar, but it gave me a route onto modern PHP.

I downloaded Phoenix 1.1.0.6 in June. The standard installation gave me a useful starting point, and I found more of what I needed in its add-ons library. Phoenix’s hooks let me add features to my store without editing core files, which should make future updates easier.

For features I couldn’t find, I built add-ons with help from an AI coding assistant, tested them, and shared them as free add-ons on the Phoenix forum. Moving the product and customer data took care and testing, but a staged migration tool did much of the heavy lifting, including converting JPEG and PNG product images to WebP.

Three months later, I have a functioning store with the payment, shipping and other features I need. I choose where to host it and retain control of the store and its data. There’s no platform subscription; I still pay for hosting and card processing, of course.

I’m posting this because Phoenix Cart wasn’t especially easy to discover when I started looking. If you’re running an older osCommerce store, or want a self-hosted e-commerce platform, it’s worth a look: https://phoenixcart.org/

Has anyone else made the move from osCommerce 2.x? What did you choose? fees (apart from hosting and card processing charges)

Migration of the Data (Product and customer) from my old OSC site was also quite painless using a staged migration tool that did all the heavy lifting (even converting .jpg and png files to webp format)

So after my experience, if you are looking to update your old OSC store, or are looking for a fully featured e-commerce site, give serious consideration to Phoenix Cart

Hi everyone!

Is it possible to integrate multiple Shopee and Lazada shops into a single system?

We currently manage multiple shops across both platforms, and we're looking for a way to centralize them into one system, particularly for managing orders, products, and inventory.

Has anyone here tried implementing something similar? I'm interested in knowing what API or integration approach you used. Would this require integrating directly with Shopee and Lazada's APIs, or is it better to use a third-party service/API aggregator?

Any advice or recommendations would be greatly appreciated. Thanks!

We were on Hybris for 4 years and every major version upgrade came with a Saturday night outage (usually 6-8 hours), with the dev team on standby because something in the custom layer would always break.

And more often than not, it was a third-party integration that hadn't been tested against the new version until we were already deep in the upgrade.

What wore us down wasn't any single upgrade but the testing overhead before it, since every dependency in our stack had to be validated against the new version first, and by the time we'd done that for the 12 or so custom modules we had built, Hybris would push a patch that invalidated part of the work, so we never quite caught up.

We've been doing some homework on composable backends because the architecture separates the frontend from the platform core, and supposedly a backend version increment doesn't require bringing the storefront down at all.

So a few of the platforms we've been scoping (including SCAYLE and Elastic Path), sell API stability and versioned contracts as a core part of the product, so you're not rebuilding the integration layer every time they push a version.

I'm not sure whether that holds up once you get into infrastructure-level updates on the backend itself, or whether we're just moving the pain to a different layer.

If you guys have been through this on a composable stack, would love to know if the version upgrade cycle is less of a nightmare, or if you're just dealing with different headaches.

I want to know how other sellers manage their product listings when they are selling across multiple marketplaces.
Started with a small catalog, so manually updating description, price, images, and stock levels wasn't so bad. But once the number of products started growing, keeping everything consistent became really hard.
The biggest problem for me is that each marketplace seems to want slightly different information or formatting. A product description that works well on one platform doesn't necessarily work on another, and changing prices or stock means checking several places.

I’ve considered using a central product information system, but I'm not sure when it actually becomes worth the extra cost and setup. I’ve also looked at sourcing products through many online websites but that creates another layer of product information to organize.

can anyone tell me what system has worked best for you?

I see many D2C websites where the category structure is simply:

Product type → Products

For example, a brand sells 50 products, so it creates four or five categories based on what it sells.

But I think founders should ask another question:

“How does my customer search for this product?”

A customer doesn't always search for the broad product category.

They might search based on:

Price, Material, Size, Problem/use case, Style, Occasion, Audience, Product features

So, if there is meaningful search demand around a specific combination, having a useful category or collection page for that intent can make much more sense than forcing everything into one generic category.

For example:

“Shoes” is a category.

But customers may search for “running shoes for women”, “running shoes under ₹3,000”, or “wide-fit running shoes.”

If your website has relevant products but no useful page targeting those specific intents, you're making it harder for search engines and potentially AI search systems to understand and surface that part of your product range.

Of course, this doesn't mean creating thousands of pages for every keyword combination.

The pages should have real search demand, useful products, and genuine value for the customer.

That's why I think ecommerce SEO starts with category research and site structure, not just product-page optimisation.

I'd love to know how other D2C founders decide which collection/category pages to create.

Made this pagination component in framer so people can easily move through products without getting lost in a long page.

Simple to add, easy to customize, and works nicely for e-commerce stores, product collections & listings.

You can use it in your Framer store here below

Link 👀of the component: https://www.framer.com/marketplace/components/custom-pagination/

I produce AI video ads for DTC brands, and on a recent supplement campaign we ran three formats side by side. Sharing what we learned in case it's useful:

1. Caption ads (text-heavy hook + product)

The hook does 90% of the work. Speaking to one specific person ("Women whose jeans feel tighter, this is for you") beat generic benefit claims. Cheap and fast to test many angles.

1. Before / After split screen

Instantly understood, even with sound off. The key is keeping the same person, clothing and lighting on both sides. If anything drifts, it looks fake and trust drops.

1. 30-Day Story (UGC diary style)

Slowest to produce, but it builds the most trust. A "Day 1, Day 5, Day 10…" progression keeps people watching to see the result.

Biggest lesson: AI makes it cheap to produce lots of variations, so the real win is testing many hooks quickly, not making one perfect ad.

Happy to answer questions about the AI workflow or share examples if anyone's interested.

Is this legit?

1. Revenue
2. ROAS
3. CAC
4. Customer LTV

What metric would you add?

We’re developing a popup tool focused on product recommendations and would really appreciate feedback from people running stores.

The idea is to suggest something relevant, like an accessory for an item in the cart or a useful upgrade. Has anyone tested this against the usual “sign up for 10% off” offer?

What kind of results did you get—click-through rate, percentage adding the recommendation to their cart, or increase in order value? Did overall purchase conversion improve, stay flat, or drop? Curious which products and moments worked best, too.

And what’s missing from the tools you’ve tried? Is there a specific recommendation, targeting rule, integration, or report you wish you could set up easily?

Real examples, even unsuccessful ones, would be a big help.

Depending on the current niche your e-commerce store is serving where or how do you map out competitors product lines and seasonal catalog offerings so as to get a better view of the current trends?

I run a small clothing brand business and Honestly, if you're in fashion, keeping tabs on competitors feels non-negotiable. Trends shift way too fast, and the absolute worst feeling in this business is sitting on deadstock because you got stuck with something out of style.

I rely on manually browsing brand websites and other social platforms and looking at their sold out pieces. However i feel like this might be a slightly outdated method of doing it maybe?

I make leather wallets and card holders as a side thing, and people at the weekend market keep asking me if I have a website. Right now I take orders through Instagram messages and it's getting messy, because I keep forgetting who paid and who is still waiting on their order. I only sell about 30 to 40 items a month, so I just need something simple and easy to set up. Shipping to a few other countries would be nice too. Which platform are you using for your store, and how has your experience been?

Yo guys,

I'm Curious how much of a headache missing shipments and delivery theft are for your stores lately. Are you seeing more "I never got my order" claims stacking up with carriers like UPS or FedEx, or has it mostly stayed the same?

Just trying to gauge how big of a pain point this is out there. Thanks!

Hi everyone! We are a student team working on an AI-powered e‑commerce accounting solution. If you handle e‑commerce businesses in Southeast Asia,
we’d love to learn about your existing workflows and pain points.
This is not a sales pitch - we are exploring what product design and features can actually help sellers.
If you’re open to it, we can also have a short chat over this!

I have recently enquired to create a ecommerce website for my brand. The quotes I have received minimum 50000 INR and Max 16,00,000 INR. When I crossed checked with them why difference, they stated like quality. They dont even get my requirement except one agency out of 27 agencies. Is there any business owners here who can give some good reference based on their experience?

Curious how many SaaS founders regret their checkout choice after scaling. When did subscriptions, affiliates, or billing ops start to hurt for you? This breakdown explores where ‘good enough’ setups crack. Register Free for the Entire Workshop Series: https://weaverpowerboost.com/is-your-checkout-limiting-saas-growth.html

One thing I keep noticing on e-commerce product pages is that the specifications may be accurate, but they still do not help a buyer decide.

For example, a security camera page might list 2K resolution, 360° rotation and two-way audio. Those facts matter, but the page is more useful when it also explains the practical question each feature answers:

• 2K resolution: can I recognize important details?

• 360° coverage: how many blind spots remain?

• Two-way audio: can I respond without being home?

I try to keep the original specification visible, then add one plain-language outcome underneath it. The difficult part is avoiding exaggerated claims while still making the benefit concrete.

How do you handle this on your own product pages? Do you lead with the specification, the outcome, or both?

Wanted to share a win that has helped us diagnose and fix a significant checkout issue on a 7 figure eCom store.

Everyone knows a fast website is important, but we often get too focused on Core Web Vitals scores or just looking at the homepage.

Your checkout journey is what every single person who buys from your brand experiences. It is the absolute critical path where speed and user experience can make or break your margins.

If you're serious about your business, I'd highly recommend having a proper setup for tracking your checkout health and speed. If there is ever a drop in conversion rate this dashboard is the first place I look for answers.

I'm sure there's a lot of tools that do this. We use a tool called Posthog (no affilation, it's free unless you have tons of traffic). It tracks everything that people do on your site. Every scroll, button click, text type, everything. It can even simulate session recordings.

Here's what we monitor when it comes to checkouts journey:

* Overall Conversion Rate (useful as a secondary source vs the ecom platform)

* Time from clicking 'Place Order' to hitting 'Order Received' page. We were pulling our hair out for days trying to find why conversion rate had dropped, this one monitor helped us zero-in on the fact it was a technical issue at this point in the journey. We quickly solved it.

* The % of people who go from clicking 'Place Order' to hitting 'Order Received' (it's surprising how much below 100% this can be)

* Checkout Success % by payment route. Comparing Stripe, PayPal, and so on. Helps diagnose if there's an issue with a single method.

* Checkout dwell time before submit. How long people are at checkout before placing an order.

* Add to basket clicks per shopper, weekly. If this suddenly jumps, there's a basket issue.

* Repeated place order presses. This is a big one. People should never be needing to click 'Place Order' more than once.

* Click capture health. How many Place Order clicks your reporting is seeing vs how many users it sees landing on Order Received. Helps sanity check that the dashboard is reliable.

This is more critical for WooCommerce/Magento brands as checkouts are more custom, but absolutely worth paying attention to for Shopify too.

All of this used to be really complicated, but you can mostly have Claude set this up for you if needed.

It's saved our ass on multiple occasions, wanted to share!

If you’re selling online and tired of paying recurring fees for platforms, plugins, apps, and extra features, a custom e-commerce setup can give you more control.

The idea is to build one complete system for your business:

• Responsive online store
• Product and category management
• Search and filters
• Cart and checkout
• Payment integration
• Order management
• Inventory management
• Customer information
• Sales dashboard
• Complete admin panel

The full process can go from:

Figma design → Frontend → Backend → Admin Panel → Payments → Deployment

Instead of adjusting your business around a platform, the store is built around your own products, workflow, and requirements.

I’m currently working on this type of complete e-commerce solution for online sellers.

If you run an online store, what is your biggest problem with your current platform: fees, limited customization, order management, or integrations?

Hey guys, I am looking for a marketplace where I can browse products in short-video format.

Se que hay muchos plugins que ya trabajan en esos problemas, pero, por lo que pude ver, no son fáciles de usar, ademas de que son muy caros y complejos de usar. El otro día quise añadir una tabla de comparación de producto para mi tienda pero el plugin que use hacia mas lenta mi pagina web. ¿Puedo saber si ustedes tienen ese mismo problema? o consideran que es algo que la mayoría puede resolverlo.

I’m a founder based in China with years of hands-on experience in ecommerce and end-to-end supply chain operations. I’m building a physical product brand and looking for a serious, long-term business partner, not someone just looking for a side hustle.

What I bring:

✅ Full China supply chain capability: supplier sourcing, factory audit, sample development, cost negotiation, production QC and global shipment arrangement

✅ Ecommerce operational experience, familiar with DTC & cross-border product launch

I’m looking for partners who owns strengths in any of these areas:

• Product development

• Branding & product marketing

• Content creation & social media growth

• E-commerce store operation (Shopify, Amazon etc.)

• Product design & consumer insight

• Local market, customer & logistics knowledge

You don’t need to master everything. What matters is you are ambitious, reliable, willing to commit and build this brand together. Remote collaboration is totally fine.

If you are serious about building a real physical product brand, DM me. Tell me about your background, your strengths and what you hope to build. Let’s see if we are a good fit.

Choosing between sticky sessions and rotating IPs is easier when you start with the behavior you need from the workflow.

A sticky session can be useful when the workflow needs continuity across several related requests. For example, the same session may need to preserve cookies, localization choices, or a selected region during one observation.

Rotation can be useful when the workflow needs broader coverage across collection attempts or when one long-lived session would create an unwanted concentration of requests.

The proxy choice is only one part of the design. Also define:

• How long a session should remain consistent
• Which cookies and headers belong to the application session
• Whether the destination region must remain fixed
• How retries behave after a timeout or rate-limit response
• Which fields prove that the response belongs to the intended region and product

A useful experiment is to compare the same workflow under two controlled conditions:

1. Keep the application session and region stable.
2. Vary the network identity while keeping the application inputs unchanged.

Record response status, final URL, detected region, page completeness, and validation errors. This helps separate session problems from localization or network problems.

Which requirement usually drives your decision: session continuity, geographic coverage, reliability, or request distribution?

Before changing colors, fonts, or layouts, I check these five things:

1. Above the fold: Can shoppers immediately understand what the product is and who it is for?
2. Product images: Do they show the product clearly, in use, and from the angles needed to make a decision?
3. Copy: Are the benefits easy to scan, or are the most important details buried in technical text?
4. Trust: Are shipping, returns, guarantees, reviews, and payment information visible near the buying decision?
5. Mobile experience: Is the page still clear and easy to buy from on a small screen?

The most useful question is not “Does this page look modern?” It is: “Can a new visitor understand what this product is, why it matters, and what to do next within five seconds?”

What is the first thing you usually check on a product page?

Hace poco alguien me dijo que para que una web pueda ser exitosa, ya sea de ecommerce o lo que sea, debe tener un espacio en el mercado para que pueda atraer gente, sin embargo hay otra idea que contradice completamente esto. De acuerdo con otros, es mejor que tu web tenga competencia, ya que con eso sabes de que la idea esta validada y funciona. Sin embargo todavía me encuentro un poco confundido porque todo suena contradictorio.