The commerce OS thatThinks.Thinks.

There are no ordinary catalog or order-count caps. Fair-use limits still protect storage, bandwidth, very large imports, abusive API activity and high-compute work.

Yes. The platform fee applies when a COD order is recorded as confirmed. Fees are collected through itemized invoices, with a daily dashboard reminder of the remaining unpaid amount. Courier shipping and COD service charges are separate.

Not as recurring entitlements. Promotions may be offered to verified eligible accounts from a separate, capped grants wallet. Merchant-funded ad spend and courier fees are separate.

Yes where the provider charges or where usage exceeds included credits. The plan price does not fund unlimited paid messaging, marketing spend or image generation.

No. This is a proposed redesign for review. Connect approved price IDs and confirm billing, tax, platform-fee and grant policies before publishing.

Plan changes are intended. Timing, proration, cancellation, refunds and treatment of over-limit resources remain subject to the final billing policy. This page does not change a subscription.

The yearly option proposes 10% off the subscription. Plan cards show the annual amount paid upfront and yearly savings in USD. The estimator shows a monthly equivalent; confirmed-order fees, top-ups, tax and provider charges remain separate. Final approved prices and renewal terms need confirmation.

All subscription, confirmed-order and add-on prices in this comparison are in US dollars (USD). The page does not quote a BDT conversion rate.

The comparison includes one storefront, unlimited basic products, SKUs and orders, core editing and manual operations. It includes no monthly automated orders, and each confirmed order carries a proposed $0.08 platform fee.

Starter proposes a $3.99 monthly subscription, 10 automated orders per month and a $0.06 confirmed-order fee. It suits merchants who want full storefront editing, a custom domain and basic automation.

Both propose advanced AI capabilities. Growth is $39 per month with 500 automated orders and a $0.05 confirmed-order fee; Scale is $149 with 2,500 automated orders, higher AI allowances, three storefronts and a $0.04 confirmed-order fee.

Yes. Every recorded order confirmation incurs its plan rate, whether the order is handled manually or through automation. Automation credits cover workflow capacity and do not pay the platform fee.

A draft or pending order is not charged. The fee applies once when Storixa records the order as confirmed, including a COD checkout that creates a confirmed order. Confirmation retries do not create another fee; automation usage is tracked separately.

No. Once an order is confirmed, its platform fee remains due even if it is later cancelled, returned or fails delivery. Cancelling a pending order before confirmation creates no fee. Genuine mistakes require an authorized reviewed correction; the original assessment remains in the audit history.

The yearly cards show a proposed prepaid annual subscription total. The estimator divides it into a rounded monthly equivalent for comparison; that number is not a promise of monthly installment billing.

The proposed 10% discount applies to the subscription only. Confirmed-order fees, optional credit packs, taxes and external provider charges are calculated separately.

Included monthly automation credits reset on renewal. The displayed automation allowances are monthly even when the subscription is billed yearly; purchased top-up expiry is disclosed separately.

Monthly included automation credits reset rather than being presented as a permanent balance. Do not assume rollover or a top-up expiry date unless it is stated in the final purchase terms.

The proposal lists packs of 25 automated orders for $4.99, 100 for $14.99 and 500 for $69. Availability and final purchase terms need confirmation; presales AI usage is separate.

Packs provide related fulfillment-workflow capacity. Confirmation attempts remain subject to call controls, and a pack does not provide unlimited presales replies, paid messages or courier services.

The comparison proposes $15 for 100 AI image sets, with up to six generated images per set, or up to 600 images. Provider availability, generation policies and final credit terms apply.

No. Additional engagement is proposed as credit- or budget-based usage. A final unit price is not listed here, and paid WhatsApp or SMS charges may be additional.

No. The estimator is before taxes, purchased top-ups and external courier, ad, messaging, calling or gateway charges. It combines the subscription with confirmed-order platform fees only.

At monthly billing, Growth is $39 plus 400 confirmed orders at $0.05 each, giving $59 before taxes, top-ups and external provider charges. Included automation allowances do not reduce confirmed-order fees.

No. The estimator and monthly/yearly buttons only change this page's illustration. They do not create charges, buy credits or modify a live subscription.

Refund eligibility, proration and the effective date of a downgrade depend on the final billing policy. This pricing page does not promise an automatic refund or account credit.

No payment details are collected here. You can compare plans and estimate costs without a card; account setup and any future paid purchase happen in the Storixa app under its own terms.

The reminder shows the remaining unpaid confirmed-order platform fees, including earlier billing periods. It stays visible while a balance remains. Open Review & pay to review invoices. It does not block basic selling or imply that a wallet was automatically debited.

Fee invoices and automation or AI credit packs are separate. Paying a fee invoice reduces the fee balance after verified payment; it does not activate a paid subscription or grant extra AI credits. Payment availability depends on the configured gateway.

No. Once a usable payment method and the order-access policy are activated for your workspace, an unpaid fee invoice can lock merchant order access after seven full days from the invoice or activation notice, whichever is later. The storefront keeps accepting orders and confirmed-order fees continue to accrue. Order details, exports and order-bearing inbox or AI history are hidden until verified payment clears overdue invoices. Billing remains accessible.

The intended workflow is to choose a theme, edit sections, add products and publish without coding. Advanced design tools depend on plan and feature availability.

The proposed Starter, Growth and Scale plans include custom-domain support. Connecting a domain may require DNS setup and ownership verification; domain purchase or renewal costs may apply separately.

Planned options include CSV/Excel catalog import and supported migrations from platforms such as WooCommerce or Shopify. Product, variant, customer, order, URL and media coverage needs checking for each source. Continuous sync is not implied.

Storixa is designed for COD and supported gateways such as SSLCOMMERZ and eligible bKash/Nagad options. Online payments depend on an approved merchant gateway account and a working integration.

The comparison proposes one storefront on Free, Starter and Growth, and three on Scale. Additional-store availability and add-on pricing require confirmation.

Additional stores are described as an add-on, but a price and account limit are not published here. Share your store count and operational needs before selecting a final setup.

Inventory and dependent variants are included across the proposed plans. Organize SKU-level prices and stock carefully so the selected size and color match the actual item you can fulfill.

Basic inventory is included across the comparison, including Free. More advanced workflows, automation usage and operational integrations have their own plan and setup conditions.

Free is listed with Core editing, while Starter and above have Full editing. The comparison describes themes, sections and responsive controls; check the app for the exact controls available before choosing a plan.

The intended storefront experience is responsive. Preview product pages, variant selection, cart and checkout at mobile widths before launch, especially after custom design changes.

Use the editor's available preview tools to review layout and content. A saved draft or local preview should not be treated as a public release; confirm the publish action and live storefront separately.

A Studio save preserves editing work; it is not proof that a merchant storefront was published. Use the supported publication workflow and verify the resulting public page.

Theme editing and commerce records serve different purposes. Before publishing a theme change, preview how product content, images, navigation and checkout appear in the new layout; migration coverage depends on the editor.

Custom-domain support is included in proposed paid plans, but buying or renewing the domain is billed by your registrar. Domain ownership and DNS access are still required.

Check domain ownership, the required DNS records and the connection status shown in the app. DNS and certificate provisioning can take time; this page does not guarantee a fixed activation window.

Confirm the hostname patterns supported by the domain-connection flow before changing DNS. Keep other services, such as email and an existing website, on their intended records.

Review product prices and stock, images, contact information, delivery rules, payment setup and policies. Test a complete checkout and verify the published domain rather than relying only on an editor preview.

Import coverage depends on the supported format and field mapping. Check SKU identifiers, variant relationships, image URLs, prices and inventory with a small sample before a full import.

Unlimited basic products does not mean unlimited bulk processing at once. Large jobs remain subject to fair-use, file-size, processing and provider limits; confirm a suitable batch approach for a large catalog.

Data export and portability are included across the proposed plans, subject to account authorization. Confirm which records, media references and formats the export covers for your intended migration.

Do not assume continuous synchronization from a one-time import. Ongoing updates, conflict handling and stock ownership need an explicitly supported integration and a clear operational setup.

Team access is listed as Basic on Free, Included on Starter and Growth, and Expanded on Scale. Confirm seat counts and permissions in the app, and give each person only the access they need.

API and webhooks are governed by rate limits and fair-use rules. The comparison shows Core access on Free and Included access on paid plans; endpoint availability and quotas need confirmation.

The comparison includes role-relevant wholesale and multi-warehouse features, with Core on Free and Included on paid plans. Availability depends on the merchant role and the supported workflow, not just selecting a plan.

An order that enters a Storixa-managed fulfillment workflow. One credit is consumed when automated processing actually begins, not just when a basic order is placed. Presales messaging and abandoned checkouts use separate engagement allowances.

Checkout, manual orders, inventory and basic storefront continue. New orders fall back to manual/rules-only handling. Purchase more credits anytime. Already-started workflows can complete.

Eligible automated orders can include up to three confirmation attempts each, within call-duration, carrier and abuse controls. Three attempts do not guarantee three answered calls. Provider contract terms must be finalized.

The proposed comparison includes dashboard AI requests, presales replies, product drafts, photography and personalized sessions. Growth and Scale include advanced AI tools with larger allowances on Scale. Usage, provider eligibility, merchant approvals and cost controls apply; extra credits and provider charges are separate.

AI can prepare campaign drafts and recommendations. Spending, publishing and other consequential changes require merchant authorization and budget and permission controls. Results are not guaranteed.

Personalization depends on eligible first-party behavior, consent, available recommendations and setup. New or unrecognized visitors receive a relevant default experience; every session is not necessarily unique.

The comparison proposes trial access on Free, 20 requests per month on Starter, 200 on Growth and 1,000 on Scale. Requests remain subject to token budgets and fair-use safeguards.

Proposed monthly allowances are trial-only on Free, 100 replies on Starter, 1,500 on Growth and 7,500 on Scale. These cover text inference; paid WhatsApp messages and other provider charges are separate.

The proposal lists trial access on Free, 10 product drafts per month on Starter, 100 on Growth and 500 on Scale. Photo parsing and expensive vision work may require additional credits.

Growth proposes 10 SKU image sets per month and Scale 50. Free and Starter list separate image credits. Generation availability and fair-use policies apply.

One set covers up to six generated images for one SKU. It is not a promise of six separate products, unlimited revisions or an unlimited number of source-image analyses.

The comparison lists no included allowance on Free, trial access on Starter, 10,000 sessions per month on Growth and 50,000 on Scale. These are eligible sessions using heavier personalization computation.

No. The comparison separates popular or rule-based recommendations, session-aware suggestions and heavier AI personalization. An advanced-session allowance is not an ordinary page-view or basic-order limit.

Starter is listed with suggestions, while Growth and Scale list the Director as included. Suggestions and proposals still need the supported review, permission and cost controls before consequential changes.

Do not treat an AI suggestion as authorization to change prices. Publishing and other consequential changes must follow merchant permissions and the supported approval workflow.

The comparison proposes three active tests on Growth and 15 on Scale, with none listed on Free or Starter. Test availability, safe rollout and reversible changes depend on the supported experimentation tools.

No. Size and variant advice can help explain available product information, but fit depends on accurate measurements, size charts and the shopper's preferences. This feature uses available engagement allowance.

Review factual claims, prices, materials, sizes, delivery promises and language before publishing. A generated draft is assistance; the merchant remains responsible for the final product listing.

Generated images should represent the item honestly. Check colors, logos, proportions and variants before use, and keep accurate source photos where shoppers need to verify the real product.

Do not assume that a failed screen result means the provider incurred no cost. Charging, retries and refunds need the final usage policy; the comparison does not promise free unlimited retries.

The comparison lists separate allowances for dashboard requests, replies, drafts, photography and advanced sessions. It does not promise that unused units can be exchanged across those categories.

No. Fulfillment automation and presales engagement use different allowances. A long conversation or an abandoned checkout is not automatically covered by one automated-order credit.

Provider availability can affect AI work even when a plan includes an allowance. Keep a manual way to handle urgent tasks, and check the app's current status instead of treating a plan as an uptime guarantee.

No. Recommendations, drafts and optimization are tools rather than guaranteed business outcomes. Results depend on products, traffic, data quality, creative, budget and merchant decisions.

The comparison does not promise unrestricted model choice. Available models, supported tasks, token budgets and provider access depend on the feature and its current configuration.

Use relevant product and business information you are authorized to share. Avoid adding passwords, API secrets or unrelated personal data to prompts, and review generated work before using it with customers.

The proposed comparison includes manual Messenger, Instagram and WhatsApp inbox access on Free and Starter, and manual plus AI access on Growth and Scale. Connections depend on approved Meta permissions, eligible accounts, messaging rules and supported APIs. Paid messages are charged separately.

Not necessarily. Social platforms may limit access to past messages. Available history, identity matching and imports depend on each platform’s permissions and supported export paths.

The planned workflow connects orders with verification, eligible courier accounts, delivery updates and COD reconciliation. Available providers, fraud checks and automation need confirmation for your plan and accounts.

The proposed connected fulfillment workflow requires an eligible merchant courier account. Storixa's platform subscription does not replace courier onboarding, service coverage or the courier's delivery charges.

No. The per-confirmed-order platform fee and the courier's shipping or COD service charges are separate costs. Include both when calculating your actual order margin.

No. Courier API access alone is not settlement authorization. Any wallet collection, invoice or courier-settlement deduction must follow an agreed and authorized billing arrangement.

Remittance timing depends on the courier and your settlement agreement. Delivered, COD collected and funds settled are separate states; this page does not promise a fixed payout date.

No. An estimate helps set expectations; a confirmed tracking milestone comes from the supported courier workflow. Keep estimated arrival and courier-confirmed status distinct when communicating with shoppers.

No. Rules and AI-assisted signals can help review an order, but they do not guarantee fraud prevention or successful delivery. Review uncertain cases and maintain a manual decision path.

No. The comparison describes up to three confirmation attempts per eligible automated order. Unanswered calls, carrier conditions, duration controls and provider terms affect what happens.

Recovery depends on available contact information, consent, channel rules and the supported workflow. Paid messages and presales AI use can consume separate allowances or provider charges.

No. Follow-up features depend on plan, channel eligibility and usage allowances. WhatsApp, SMS or other provider charges can apply even when the workflow itself is included.

Online payment methods depend on an eligible merchant account and a working integration with the provider. A Storixa plan does not guarantee gateway approval or waive processing fees.

Connection support depends on eligible platform assets, approved permissions and supported APIs. Do not assume that a personal profile has the same integration access as a Page or professional account.

Expired or revoked access, account eligibility changes, platform permissions and messaging restrictions can interrupt a connection. Review the connection status and restore authorized access through the supported flow.

No. Messenger, Instagram and WhatsApp connections remain subject to each platform's permissions, eligible accounts and messaging policies. A unified view does not grant unrestricted messaging rights.

No. AI campaign tools and optimization are separate from merchant-funded ad spend. Your eligible ad account, permissions, approved budget and Meta charges still apply.

A draft is preparation for review. Publishing an ad or spending a budget requires merchant authorization, supported account permissions and the appropriate budget controls.

The comparison lists Meta Pixel and basic CAPI on all plans with an eligibility marker. Setup, usage conditions and the provider's integration requirements still apply.

Reporting depends on the events collected, consent, browser behavior and connected sources. Missing signals and attribution limits can create differences; operational order and payment records should be checked separately.

The proposed event/report history is seven days on Free, 30 on Starter, 90 on Growth and 180 on Scale. These reporting windows do not define retention of durable financial records.

The comparison lists self-serve support on Free, email on Starter, standard support on Growth and priority on Scale. No response-time or uptime SLA is implied without a separate contract.

Share the affected store, relevant order or connection reference, time, expected behavior and the error shown. Remove passwords, provider tokens and unrelated customer details before sending screenshots or logs.