Filipino small businesses live on social media. Your favorite milk tea shop? It probably runs on Facebook Page messages and TikTok videos. Not a website.
So when those shops start buying boosts for their posts, things get chaotic fast. Screenshots in Messenger. Orders tracked in a notebook. Payments scattered across GCash receipts.
This post shows a simple Node.js setup that fixes that. We'll send orders to an SMM panel API, store them and show a clean status board. Nothing fancy. Just practical.
Why a tracker even matters
Here's the thing. A shop owner doesn't care about API responses. She cares about three questions:
- Did my order start?
- How much is done?
- Did I get refunded for anything that failed?
Answer those clearly and you've built something people will actually use.
The API shape
Most panels serving the Philippines use the standard v2-style API. One URL, one key and an "action" field. You send form data. You get JSON back.
The actions that matter for tracking:
- add – creates an order and returns an order ID
- status – checks one order or a batch
- services – lists what you can buy, with peso rates per 1,000
Setting up the project
Keep it minimal. Node 18 or newer has fetch built in. So no axios needed.
mkdir order-tracker cd order-tracker npm init -y npm install better-sqlite3 express SQLite is perfect here. One file. No database server. A small shop will never outgrow it.
The panel client
// panel.js const API_URL = process.env.PANEL_URL; const API_KEY = process.env.PANEL_KEY; async function panel(action, extra = {}) { const body = new URLSearchParams({ key: API_KEY, action, ...extra }); const res = await fetch(API_URL, { method: "POST", body }); if (!res.ok) throw new Error("Panel error " + res.status); return res.json(); } async function addOrder(service, link, quantity) { return panel("add", { service, link, quantity }); } async function getStatus(ids) { return panel("status", { orders: ids.join(",") }); } module.exports = { addOrder, getStatus }; Keep the key in an environment variable. Never commit it. Leaked keys on public repos get scraped surprisingly fast.
Storing orders
// db.js const Database = require("better-sqlite3"); const db = new Database("orders.db"); db.exec( "CREATE TABLE IF NOT EXISTS orders (" + "id INTEGER PRIMARY KEY, customer TEXT, platform TEXT, " + "link TEXT, quantity INTEGER, status TEXT, " + "start_count INTEGER, remains INTEGER, charge REAL, " + "gcash_ref TEXT, updated_at TEXT)" ); module.exports = db; Notice the customer and platform columns. Shop owners often run boosts for several pages at once. Grouping by customer saves a lot of scrolling later.
The sync job
Now the heart of it. Every 15 minutes, grab open orders and ask the panel for updates.
// sync.js const db = require("./db"); const { getStatus } = require("./panel"); async function sync() { const open = db.prepare( "SELECT id FROM orders WHERE status NOT IN ('Completed','Canceled')" ).all().map(r => r.id); for (let i = 0; i < open.length; i += 100) { const batch = open.slice(i, i + 100); const result = await getStatus(batch); for (const id of batch) { const s = result[id]; if (!s || s.error) continue; db.prepare( "UPDATE orders SET status=?, start_count=?, remains=?, charge=?, " + "updated_at=datetime('now') WHERE id=?" ).run(s.status, s.start_count, s.remains, s.charge, id); } } } setInterval(sync, 15 * 60 * 1000); Batches of 100 keep you friendly with rate limits. And skipping errors per order means one bad link won't block the rest.
A simple status board
Express plus one route is enough:
// server.js const express = require("express"); const db = require("./db"); const app = express(); app.get("/orders/:customer", (req, res) => { const rows = db.prepare( "SELECT * FROM orders WHERE customer=? ORDER BY updated_at DESC" ).all(req.params.customer); res.json(rows); }); app.listen(3000); Plug that into any tiny frontend. Or even a Google Sheet through a fetch script. Shop owners love sheets. Don't fight it.
Philippine-specific gotchas
A few local things worth knowing:
- Peso pricing. Show ₱ everywhere. Converting from dollars confuses buyers and hurts trust.
- GCash and Maya receipts. Store the reference number with each order. Disputes get settled in seconds.
- Messy Facebook links. Links shared from the app often carry tracking parameters. Strip query strings before sending them to the panel.
- TikTok profile vs. video links. Followers need a profile link. Views need a video link. Validate before you call add.
If your client is chasing TikTok income, read up on TikTok monetization in the Philippines first. It helps you set honest expectations about what boosts can and can't do for payouts.
Choosing an upstream panel
Your tracker is only as good as the panel behind it. When I compare options for PH clients, I look for:
- Clear peso rates per 1,000
- Refill on services that tend to drop
- An API page that actually documents the fields
- Support that replies within a day
BoostingPH is the one I use as a reference point for the local market. Their boosting site Philippines guide lists real prices and explains what each quality tier means. That's handy when you're setting margins inside your own app.
You can also check the full catalog at https://boostingph.com/services and grab real service IDs for testing.
A note on honesty
Meta and TikTok don't officially endorse paid engagement. Their terms let them remove inauthentic activity. So be upfront with clients. Boosts can add social proof. They can't replace good content. Say that out loud and clients will trust you more, not less.
Final thoughts
You don't need a giant SaaS to help a local shop. A SQLite file, a sync job and one Express route go a long way. The code takes an afternoon. The real value is clarity: owners finally see what they paid for and where it stands.
Build it once. Reuse it for every client after that.
Written by MD Fozla Rabbi, SEO Specialist.