ecommerce

Audit ecommerce cart-to-checkout workflows for correct backend totals and payments.

3|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/doedoe123-boop/negosyohub --skill ecommerce-doedoe123-boop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ecommerce
Source: https://github.com/doedoe123-boop/negosyohub/tree/main/skills/ecommerce
Command: npx skills add https://github.com/doedoe123-boop/negosyohub --skill ecommerce-doedoe123-boop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you implement and troubleshoot end-to-end ecommerce flows so pricing, discounts, payments, and commissions stay consistent and correct across storefront, API, and panels.

Core Features & Use Cases

  • Storefront browsing & cart integrity: Keeps product/variant/category browsing and cart behavior correct within the single-store constraint.
  • Checkout, payments, and order placement: Ensures addresses, shipping/payment method selection, and order state transitions (including COD) are handled safely and consistently.
  • Discounts, commissions, and reviews: Applies backend-only coupon/discount calculations, preserves commission/payout logic, and clarifies review type (product, store, or both) before changing UI/policies.
  • Use case: Fix a checkout bug where the customer sees one total but the order records another by validating backend totals, authorization, and SPA-to-API synchronization.

Quick Start

Use the ecommerce skill to audit the cart-to-checkout-to-order workflow for correct backend totals, payment method/state handling, and commission/payout calculations.

Frequently Asked Questions about ecommerce

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure checkout totals match between the storefront and the backend API?

To ensure checkout totals match, enforce server-side total authority so the backend calculates the final cart totals independently of client-side displays. This prevents SPA-to-API synchronization mismatches where customers see one total but order records show another.

How do coupon code discounts and commissions stay consistent during order placement?

Coupon code discounts and commissions stay consistent by applying backend-only discount calculations and preserving payout logic throughout the checkout progression. This ensures commission calculations remain accurate even after promo codes modify the final cart total.

How do I handle Cash on Delivery and PayPal payment method selection safely?

Handle Cash on Delivery and PayPal selection safely by maintaining a strict separation between payment_method and payment_status fields during checkout state transitions. This ensures the order accurately records the selected payment method while tracking its fulfillment status independently.

How do I prevent cross-store or cross-customer data exposure in a multi-sector marketplace?

Prevent cross-store or cross-customer data exposure by implementing secure API and panel scoping that enforces the single-store constraint. This ensures cart mutations, order history, and order details remain strictly isolated to the authenticated customer and their specific store context.

What is the best way to audit cart mutation and checkout progression workflows?

The best way to audit cart mutation and checkout progression is to validate backend totals, authorization checks, and payment state handling from cart addition through order placement. This end-to-end verification catches discrepancies in product variants, addresses, and shipping selections.

When should I separate product reviews from store reviews in an ecommerce marketplace?

Separate product reviews from store reviews when your marketplace policy requires distinct feedback collection for the item purchased versus the seller's service. Clarify the review type before changing UI components to ensure the review data correctly maps to the target entity.