Member Avatar for yassir.arafat.73

Hello,

If you don’t mind I want to ask you some questions regarding ecommerce platforms.

Our team is developing now a new webstore solution (startup) that should be launched in August and I am strongly interested in your opinion, guys.

  1. If you are already using any of eCommerce platforms, what advantages and benefits can make you transfer to another one?

  2. Are you satisfied with support, if it is provided?

  3. What were the main difficulties you come across while building your webstore?

Your opinion really matters and will help me greatly.

  • 5 Contributors
  • 4 Replies
  • 236 Views
  • 6 Months Discussion Span
  • Latest Post Latest Post by susanjeff

Dani AI

Generated

Brief, practical summary that synthesizes the thread (questions from , the support point from , and ’ note about plugins) and gives action-oriented guidance for a new webstore platform.

Platform-change triggers (measure these first)

  • Growth limits: inability to scale during peak traffic, or missing APIs/integrations that block key workflows.
  • Total cost of ownership: recurring app/add-on fees + hosting + developer hours > expected ROI.
  • Security / compliance: if your platform can’t meet payment-card controls or force costly workarounds, that’s a showstopper.
  • Operational risk: frequent outages, lost orders, or checkout errors.
    These are common catalysts for replatforming — assess metrics (uptime, cart-abandonment, page response times, cost-per-feature) before deciding. (wpengine.co.uk)

Realistic support expectations

  • Treat platform support as scope-limited: platform teams fix platform bugs and infrastructure; they rarely implement bespoke business logic. As suggested, plan for third‑party dev resources for code-level fixes.
  • Require an SLA that covers uptime, escalation steps, and access to logs, plus a staging environment and rollback plan.

Common build problems and practical mitigations

  • Integrations (ERP/CRM/POS): build an API-first integration layer and mock test data early.
  • Taxes/shipping/fulfillment rules: model edge cases in staging and automate tax rules where possible.
  • Checkout customizations and payments: design the minimal viable checkout flows first; validate with real payment test cards and ensure PCI scope is minimized. ()
  • SEO preservation on migrations: map every URL, implement server-side 301s, avoid redirect chains, and monitor Search Console during cutover. Example (Apache): 
# permanent redirect for one product
Redirect 301 /old-product-slug https://www.example.com/products/new-product-slug

Follow Google’s site-move guidance and use Search Console to track reindexing. (developers.google.com)

Product strategy advice for a startup builder

  • Don’t try to out-ecosystem giants by cloning hundreds of plugins. Focus on 1–2 vertical problems, build excellent APIs/webhooks, and offer specialized integrations or managed services (this echoes ’ practical approach). Large marketplaces like WooCommerce and Adobe Commerce demonstrate why a huge extension ecosystem matters; niche focus + great extensibility is more defensible for a new platform. (wordpress.org)

Quick checklist to include in your roadmap

  • Define measurable migration triggers and KPIs.
  • Publish clear SLA and support boundaries.
  • Build API-first, document webhooks, and provide a staging/rollback path.
  • Automate tests for checkout, tax, shipping, and backups.
  • Plan an SEO/redirect strategy and verify with Search Console. (wpengine.co.uk)

Recommended Answers

All 4 Replies

Member Avatar for Member #949455

Your opinion really matters and will help me greatly.

I don't think my opinion really matters what platform you are using. The reason is very simple.

If you setup the website and all your code is working then there's not issue.

It's kinda like iffy-iffy when it comes to tech support for e-commerece platform.

They can only assist you only half way.

Member Avatar for Manish02

Hello everyone,
yes i agree with you Lastmitch.

Member Avatar for midynamics

We developed our ecommerce CMS using Zend and adapting the best features from Opencart and Magento. The outcome was a highly reliable, secure and scalable CMS.

However, there's no way our product could compete with Open source CMS's like Opencart, Magento, OScommerce etc. Why? Because you just cannot develop 100s of plugins that meet the requirements of your customers.

We only use our product only when a client's required a bespoke feature/functionality for which a plugin's not available or would take forever to develop one.

Anyway, all the best & good luck.

Member Avatar for susanjeff

make the google adwords this is the best plan to get the business this is the best thing

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.