How KyoskGo Vendor Plans and Limits Work

Software pricing is frustrating when the marketing page says “unlimited” but the dashboard quietly blocks you—or when a button appears but the API returns forbidden.

KyoskGo uses subscription plans with explicit **features** and **limits**, enforced in backend middleware and services, not only hidden in React components.

This article explains how that works so vendors can choose a plan honestly and customers are not misled about what a business can actually do.

What a vendor plan controls

Each subscription plan defines:

• **Name and slug** (for example free, pro, enterprise in default seed data).
• **Price and billing interval** for the vendor’s KyoskGo subscription (distinct from how that vendor collects money from their own customers).
• **Feature list:** capability keys such as items, orders, invoices, payments, bookings, customers, analytics, multi_business, packages, dynamic_fields, api_access, priority_support.
• **Limits:** numeric caps such as `maxItems`, `maxBusinesses`, and media storage bytes where configured.
• **Trial days** when applicable.
• **Transaction fee percent** where used in commercial terms.

Your live deployment may show different plan names or prices than examples in documentation. Always check the in-app plan picker and account settings for current values.

Plans are for vendors, not for end customers

End customers ordering cake or booking a haircut do not pick a KyoskGo SaaS plan. They interact with a business profile.

The subscription applies to the **vendor account** that operates one or more businesses on the platform.

Feature gates: what “included” really means

A feature key must be present on the active subscription for routes and APIs behind that feature to succeed.

Examples:

• Without `bookings`, booking APIs and flows should not work even if someone guesses URLs.
• Without `invoices`, invoice creation endpoints reject unauthorized feature use.
• Without `multi_business`, adding a second business may hit limits or feature checks.

The UI should hide actions you cannot use, but **security relies on the server**. That protects customers from broken experiences and protects the platform from bypass tricks.

Limits: when you hit the cap

Common limits include:

• **maxItems:** how many catalog items you can create across the business.
• **maxBusinesses:** how many business profiles one vendor account may operate.
• **maxMediaBytes:** storage budget for uploads where enforced.

When you reach a limit, creation endpoints should fail with a clear error—not silently corrupt data. Upgrade the plan or remove unused items.

Default seed data in development often includes a free tier with modest caps and paid tiers with higher caps. Production numbers may differ after admin configuration.

Trials and inactive subscriptions

Plans may include trial periods. During trial, feature sets typically match the subscribed plan tier.

If a subscription lapses or is inactive:

• Vendor dashboards may restrict create/update actions.
• Public storefronts may need careful handling so existing customers are not abandoned without notice—check your deployment’s policy for unpublished vs read-only behavior.

Do not assume “trial expired” only hides menus. APIs should enforce the same rules.

What plans do not limit (by themselves)

Subscriptions gate platform capabilities. They do not replace:

• **Your responsibility** for product quality, delivery, and customer service.
• **Local payment methods** your business configures (UPI, cash, bank transfer).
• **Search ranking**, which still depends on profile quality, reviews where real, and useful public content.
• **Legal compliance** for your industry and region.

Choosing a plan practically

Start on free or trial when:

• You are validating one business and a small catalog.
• You need profile, items, and basic orders before hiring staff.

Consider upgrading when:

• You hit item or business limits regularly.
• You need bookings, invoices, advanced analytics, or API access feature keys on paid tiers.
• You operate multiple brands under one vendor login and need `multi_business`.

Enterprise-style needs when:

• Many businesses, large catalogs, or custom commercial terms apply.
• You require lower transaction fee percentages defined on the plan record.

Honest comparison table (conceptual)

| Concern | Free / entry tier (typical) | Paid tier (typical) | |--------|-----------------------------|---------------------| | Public profile & catalog | Yes, within item limits | Higher limits | | Orders & checkout | Usually core | Usually core | | Invoices & payments | Feature-gated by plan | Often included on paid | | Bookings | Feature-gated | Often included | | Multiple businesses | Low limit | Higher limit | | Enforcement | Server-side | Server-side |

Exact rows for your account appear in subscription settings—not in this blog post.

For customers: what to expect

If a business page shows booking or ordering, that business’s vendor should have an active plan and features that allow it. If something fails with a permission error, the business may need to upgrade or fix subscription status—not you as the customer.

Related reading

• Create a business profile online
• How to manage local orders as a small business
• How to set up online booking for a salon or service business

FAQ

Can I hide a feature in CSS and still use it?

No. That is unsafe and should not work against protected APIs.

Do plan limits count deleted items?

Implementation details may vary; treat limits as active records unless your dashboard shows otherwise.

Is vendor subscription billing the same as customer order payment?

No. Vendor plans bill you for using KyoskGo. Customer payments flow through your business’s order and invoice configuration.

Who changes plan definitions?

Administrators maintain plan records. Seeded defaults exist for development; production may be customized.

Where do I see my current usage?

Use vendor account and subscription screens in the dashboard. If usage meters are not visible, watch for errors when creating items or businesses—that often means you are at the cap.