The challenge
As a store grows, it needs workflows that standard settings cannot cover.
The UP module collection addresses needs found in Botble store administration: organizing products, working with variations and applying promotional rules. This case focuses on improvements to the catalog and dashboard. Payment integrations have separate case studies with their own workflows and validation limits.
The approach adds features through modules and extension points, while considering adaptations for SaaS stores. The focus is the behavior that store operators need to control. Each feature depends on the platform version, installed modules and business rules used by the store.
How the workflow works
- 01
Identify the operating rule
Catalog requirements became specific features: promotion dates, category rules, variation management and a simpler product-entry interface. This defines the problem each module needs to address.
- 02
Extend the dashboard
UP modules provide their own settings and connect to the platform. The documented work includes UP Products features for managing the catalog and promotions within the store’s workflow.
- 03
Check the behavior
Saving changes was checked in a test environment. The audit also records a variation-cache fix validated across different combinations without modifying the platform’s core.
- 04
Account for the SaaS environment
Later adaptations considered operation by store. Compatibility must be reviewed during installation because the theme, version and other modules form the environment in which each feature runs.
The work
UP modules with their own settings, integrated through the platform’s extension points.
- Catalog, variations and promotion rules
- Checkout, Pix and Mercado Pago integration
- Modular customization that preserves the base
Clear rules for catalogs and promotions
A promotion involves more than changing a number. Its dates and selected categories need to reflect the store operator’s intent. The documented work brings together controls for those rules and changes to the product-entry interface, connecting configuration to the operational workflow.
For product variations, the displayed information needs to follow the selected combination. The recorded cache fix illustrates a targeted improvement: review behavior that affects the catalog experience and check the combinations involved.
A modular approach to store development
Organizing customization into modules helps define the responsibility and settings of each feature. The project uses Botble and its extension mechanisms. It does not present the original platform as Upmy’s creation or assume automatic compatibility with every installation.
The documented result is a collection of features implemented and tested in development environments, with SaaS adaptations. For another store, the next step is to review the environment and define which rules should be retained, adjusted or added in the proposal.
Delivery and context
Features implemented and tested in development stores, with adaptations for a SaaS environment.
Deployment considerations
- Compatibility with platform versions, themes and updates is reviewed before each deployment.
- Botble and third-party foundations retain their own licenses and authorship.
Frequently asked questions
Can I request just one catalog improvement?
Yes. A proposal can address one specific rule after a review of the platform and expected behavior. Installing every module shown here is not assumed.
Will these modules work with any Botble store?
Compatibility depends on the version, theme, plugins and existing changes. Those details need to be checked before installation or adaptation to a new environment.
A similar workflow in your business?
Tell me which platform you use, how your workflow operates today and what needs to change. Together, we can define the scope, integrations and acceptance checks for your project.
Request a quoteScope and pricing tailored to your project.