SOP · Internal Process
Bug Reports & Improvements
to Wappsi
One single channel, one single log, zero uncertainty about the status of each request.
Owner: Pablo
Process
Internal
One single channel, one single log, zero uncertainty about the status of each request.
Ensure every improvement or problem is documented with enough detail for Wappsi to act quickly, and that the team can see the status of each request without having to ask "so what happened with that?"
Any team member who finds a bug or has an improvement idea fills out the format below and sends it to Pablo via WhatsApp or email — the channels Wappsi already uses. Do not report directly to Wappsi without going through Pablo, so there's a single coordination and priority point.
| Field | Example |
|---|---|
| Date | 07/15/2026 |
| Reported by | Name |
| Type | Bug / Improvement / Technical Question |
| Problem description | What happened, what was expected |
| Screenshot | Required if applicable |
| Exact URL | Required if applicable |
| User who experienced it | Name / seller or buyer account |
| Urgency (per reporter) | High / Medium / Low |
Pablo maintains a sheet (Google Sheet or Notion — to be decided with Kriston) with one row per report:
| Date | Reported by | Short Description | Status | Response Date | Notes |
|---|---|---|---|---|---|
| Sent to Wappsi · In Progress · Resolved · Rejected | |||||
This log is visible to the whole team (shared link) — so nobody has to ask Pablo one by one "did they fix X yet?" You can see the status directly.
Wappsi doesn't have a confirmed fixed SLA yet. Pablo's task — tomorrow (07/16/2026): formally ask Wappsi how long improvements/bugs will take once reported, depending on the type of request (critical bug vs. improvement).
Stock does get deducted automatically and in real time when a sale occurs. Own-brand inventory (Do Brasil, Uptrend, Hello Kids) syncs with the ERP; external sellers' stock does not sync — and doesn't need to. Gives Laura/Inventory complete peace of mind: nothing to manage there.
Today, when a product reaches 0 units, it remains visible in the storefront (you can't buy it, but it's not marked either), which confuses the buyer. We'll request Wappsi to add an automatic label. Priority: Medium-High — affects the buying experience, not just aesthetic.
Confirm which system notifications are not working (mentioned by the team).
Evaluate feasibility — so CSR knows in real-time when to request verification photos from the seller, without having to manually check the "New Arrivals" page.
Pablo asks how long improvements will take once reported. Priority: High — it's the foundation for communicating real timelines to the team and reducing the anxiety of "when will this be fixed?"
Pablo documents the platform's basic processes (how to create a product, how to bulk upload, how to customize the store, how to set up payout, how to create coupons, how to request a new category). This documentation has dual use: