Custom e-commerce development

Custom e-commerce is when cart, stock, shipping, and settlement must be yours. A pretty theme without a warehouse panel is a shopfront. KGSM puts catalog, cart, gateway, invoice, and order status on one dataset.

Audience, risk, and how KGSM works

A shop or brand that has outgrown a WordPress theme on partner pricing, stock, and gateways

Theme shops take wrong orders when real pricing and stock arrive, and gateway mismatches last weeks.

KGSM builds Laravel shops with an operations panel, Iranian gateways, and stock; the theme is not the sales engine.

Sales engine, not a theme

Partner pricing, wholesale minimums, and weight-based goods die in plugin collisions. In Laravel they are domain code. Stock decrements or reserves in the moment so two checkouts cannot sell one serial. The packing panel is not the storefront. Zarinpal unique ids and daily matching belong in version one.

Reserve or decrement stock in the moment. WooCommerce with five wholesale plugins froze the cart on Black Friday.

Order, ship, return

Statuses must be readable: paid, warehousing, shipped, returned. Weight or province shipping is a discovery item. Returns must restore stock and post finance or profit is fiction. Wholesale and retail share a catalog with role-based price lists — not two shops.

Two simultaneous checkouts sold one serial twice because stock only dropped at night. Make order statuses readable for support.

Gateways and mismatches

Gateway success with a failed order means double deposits. Webhooks, user return, and a daily reconcile job sit in version one. Fees live on the receipt. Spot-price goods need a cart price lock with a timeout.

Store gateway fees on the receipt. Returning from the gateway created no order; the customer had a receipt and the warehouse did not.

After launch

A living shop reviews returns, cart abandonment, and negative stock weekly. Coupons and loyalty wait until settlement is stable. A mobile app uses the same API. Blog content stays away from the order engine so writers cannot break price.

Manual provincial shipping in Excel disagreed with the cart. Automate daily gateway matching.

Returns must post stock and finance. A return did not restore stock and extra purchases were made.

A blog author typed a price that disagreed with the panel. Put partner prices on the customer role, not a hidden coupon.

Keep the packing panel off the storefront. WooCommerce with five wholesale plugins froze the cart on Black Friday.

Two simultaneous checkouts sold one serial twice because stock only dropped at night. Lock spot prices in the cart with a timeout.

Implementation checklist

• Reserve or decrement stock in the moment.
• Make order statuses readable for support.
• Store gateway fees on the receipt.
• Automate daily gateway matching.
• Returns must post stock and finance.
• Put partner prices on the customer role, not a hidden coupon.
• Keep the packing panel off the storefront.
• Lock spot prices in the cart with a timeout.

Field scenario 1

WooCommerce with five wholesale plugins froze the cart on Black Friday.

Reserve or decrement stock in the moment.

Field scenario 2

Two simultaneous checkouts sold one serial twice because stock only dropped at night.

Make order statuses readable for support.

Field scenario 3

Returning from the gateway created no order; the customer had a receipt and the warehouse did not.

Store gateway fees on the receipt.

Field scenario 4

Manual provincial shipping in Excel disagreed with the cart.

Automate daily gateway matching.

Field scenario 5

A return did not restore stock and extra purchases were made.

Returns must post stock and finance.

Field scenario 6

A blog author typed a price that disagreed with the panel.

Put partner prices on the customer role, not a hidden coupon.

Approximate investment

A first custom shop (catalog, cart, gateway, order panel) often starts in the tens of millions of tomans. Spot prices, wholesale, and multi-warehouse add cost. WordPress is cheaper until the first special rule.

FAQ

Is WordPress enough?

For a shopfront and articles, yes. Partner pricing, live stock, and complex settlement usually need a Laravel shop.

Do you integrate Iranian gateways?

Yes — Zarinpal and similar. Unique ids and webhooks are in version one.

Can you build a gold shop?

Yes — price locks and live stock. See the jeweler industry page.

What is in version one?

Catalog, cart, payment, stock, order panel. Loyalty and apps wait until settlement is stable.

Related KGSM pages

• برنامه‌نویسی وب KGSM
• تماس و برآورد

When you apply this on a live team, write it as an operating rule, not a slide: Reserve or decrement stock in the moment. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Make order statuses readable for support. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Store gateway fees on the receipt. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Automate daily gateway matching. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Returns must post stock and finance. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Put partner prices on the customer role, not a hidden coupon. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Keep the packing panel off the storefront. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Lock spot prices in the cart with a timeout. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: WooCommerce with five wholesale plugins froze the cart on Black Friday. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Two simultaneous checkouts sold one serial twice because stock only dropped at night. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Returning from the gateway created no order; the customer had a receipt and the warehouse did not. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Manual provincial shipping in Excel disagreed with the cart. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: A return did not restore stock and extra purchases were made. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: A blog author typed a price that disagreed with the panel. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Theme shops take wrong orders when real pricing and stock arrive, and gateway mismatches last weeks. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: KGSM builds Laravel shops with an operations panel, Iranian gateways, and stock; the theme is not the sales engine. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: A shop or brand that has outgrown a WordPress theme on partner pricing, stock, and gateways Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: A first custom shop (catalog, cart, gateway, order panel) often starts in the tens of millions of tomans. Spot prices, wholesale, and multi-warehouse add cost. WordPress is cheaper until the first special rule. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Reserve or decrement stock in the moment. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Make order statuses readable for support. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Store gateway fees on the receipt. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Automate daily gateway matching. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Returns must post stock and finance. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Put partner prices on the customer role, not a hidden coupon. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Keep the packing panel off the storefront. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Lock spot prices in the cart with a timeout. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: WooCommerce with five wholesale plugins froze the cart on Black Friday. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Two simultaneous checkouts sold one serial twice because stock only dropped at night. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Returning from the gateway created no order; the customer had a receipt and the warehouse did not. Then assign an owner and a review date so the rule survives the first busy week.