REDIS.4U modules

Planned

Bolt-on power for the flagship.

IN-OUT runs the clock, the routes and worker pay. PAY-PRO runs the money coming in and the money going out. Both plug into REDIS.4U, both post to QuickBooks, and no payment moves until a person releases it.

Join the modules waitlist See build status

Build specs are written. Not available yet — on the roadmap, marked Planned until they ship.

Render: money and time flowing through the warehouse On the left, three sources: a locked tablet time clock beside loading dock 2, a delivery truck on Route 4 with a fuel stop, and a driver's phone photographing a customer check. Glowing lines from all three converge into a hexagonal REDIS.4U core ringed with the words "AI can read, match and suggest. It cannot release money." From the core a single line runs into an amber gate marked Human release, with a key switch turned by a named person. Only past the gate does the flow split to QuickBooks, the book of record, and to your own bank. DOCK 2 IN-OUT 06:58 CLOCK IN Time clock at the dock PIN + photo · kiosk locked R4 Route 4 · fuel at clock-out Stops, hours and fuel tied to one driver shift PAY TO THE ORDER OF $ ▒▒▒ ⑆ ▮▮▮▮ ⑆ ▮▮▮▮▮▮ ⑈ 1042 READ ✓ Check photographed at delivery HOURS ROUTE + FUEL CHECKS AI CAN READ · MATCH · SUGGEST — IT CANNOT RELEASE MONEY · AI CAN READ · MATCH · SUGGEST — REDIS.4U VERIFY · MATCH · PROPOSE PROPOSED HUMAN RELEASE HOLD RELEASE A named person turns the key QuickBooks Book of record POSTED ✓ Your bank Your own account We never hold it

Product render · sample scene · modules planned

IN-OUT · workforce time, route & pay

Planned

Punch in. Punch out. Paid right.

A locked tablet at every location takes the punch. Hours roll up by workweek with overtime, drivers' time ties to the route they ran, and the pay run climbs a two-person approval chain before a cent leaves your account.

One tablet per location. Locked down.

Workers clock in and out on an Android tablet fixed at each location, with a PIN and a photo on every punch. The tablet runs only IN-OUT, it's registered to its location, and punches from anything else are refused.

  • Exact timestamps, no rounding. Hours to two decimals.
  • Missed punches entered by a manager, with a reason, and shown as edited everywhere.
  • Pay groups and job titles, per-worker rate overrides, and one worker's hours split across groups at different rates.
  • Every report exports. The payroll register matches to the cent.

Sample  Worker 1 · Main warehouse

Drivers clock out with the route in hand.

A driver's time is tied to the delivery route they ran that day. At clock-out the kiosk asks about fuel, shows the route summary to confirm, and asks how many customer checks they're turning in.

That count is compared with the check photos the driver took at each stop. A mismatch flags AR and the manager before the driver leaves, and it feeds straight into PAY-IN PRO.

The pay run

Four steps. Two people.

The week closes, IN-OUT drafts the pay run with its flags, and it moves through this chain in order. Nothing skips a step.

  1. Warehouse manager

    Verify

    Approve, modify with a reason, or reject each line. Flags surface first: edited punches, long shifts, check mismatches.

  2. Comptroller

    Approve

    Approves the run or sends lines back with a comment. Must be a different person from the manager.

  3. PAY-OUT PRO

    Pay

    One payout per worker, released by a person, from your own account.

  4. QuickBooks

    Post

    Posted to QuickBooks and the run locks. Corrections go into next week, never into a paid run.

Two-person ruleThe system blocks the same user from verifying and approving. Every change keeps who, what, the old and new value, and why.

PAY-PRO · PAY-IN PRO

Planned

Get paid. Stop typing it in.

Customer money arrives three ways. PAY-IN PRO matches every payment to the right invoices and posts it to QuickBooks, so nobody hand-keys payments at the end of the day. The money goes straight to your bank.

  • Paper checks

    Photographed by the driver at delivery, counted at clock-out, scanned once by AR, matched and applied, then deposited to your bank.

  • E-check & Autopay

    One-time bank payments or Autopay through the customer portal. Applied to the invoices automatically.

  • Cards

    Paid in the portal. Where it's allowed, the card surcharge passes to the customer automatically.

Render: a customer check feeding through a desktop check scanner while an amber beam reads its MICR line. Sample data. CUSTOMER B SAMPLE CHECK No. 1042 PAY TO THE ORDER OF 1,240.25 MEMO INV-1041 / 1047 / 1052 ⑆▮▮▮▮▮▮▮▮⑆ ▮▮▮▮▮▮▮ ⑈1042 CHECK SCANNER Front, back + MICR line READ Check 1042 Amount 1,240.25 Ready AR scans the batch once Sample check · Customer B · illustrative amounts

A check's journey

  1. Photo

    The driver photographs the check at delivery. It's linked to the customer, route and stop.

  2. Count

    At clock-out the driver enters how many checks they're turning in. Mismatches alert AR.

  3. Scan

    AR feeds the batch through the scanner once. Front, back and MICR line captured.

  4. Match

    Each check is matched to open invoices and credits. Exact matches are pre-approved; the rest are flagged.

  5. Deposit

    Payments post to the exact invoices in QuickBooks, and the batch deposits to your bank.

PAY-PRO · PAY-OUT PRO

Planned

Money leaves when a person says so.

Open QuickBooks bills, listed by due date. AP picks what to pay, PAY-OUT PRO builds the payout run and raises red flags, and a named approver releases it from your own account. Every payment posts back as a linked bill payment.

Four red flags, raised before anyone releases.

A flagged line can't slip through as one row in a long list. It's held, labelled, and waits for the approver to look at it.

  • New payeeFirst time paying this vendor.
  • Bank changedBank details changed in the last 30 days.
  • Over 2×Amount over twice the vendor's 90-day average.
  • DuplicateA bill number that's already been paid.

Same-day bills to one vendor combine into one payout with the bill list attached. Worker pay from IN-OUT needs two approvers: the manager in IN-OUT and the comptroller in PAY-OUT PRO.

Shared by PAY-IN PRO and PAY-OUT PRO

Rules money obeys.

These aren't settings you can switch off. They're how PAY-PRO is being built.

  • We never hold your money.

    Customer payments land in your bank. Payouts leave from your own account. REDIS.4U sits beside the money, never in the middle of it.

  • Humans release money.

    AI can read, match and suggest. It cannot create, change or release a payment.

  • Documents are data, not instructions.

    Whatever an email, a bill or a check image says, it's read as information. It never tells the system what to do.

  • Bank changes wait.

    A change to bank details needs a callback to a number already on file, a second person's approval, and a 24-hour hold.

  • QuickBooks is the book of record.

    Every payment posts once, to the exact invoices or bills it pays. Run it twice and it still posts once.

  • No full account numbers.

    We don't store them. You see the last four digits; what we keep is encrypted at rest.

Also on the module roadmap

One is lit. Three are coming.

More modules that bolt onto the same customer master. Each chip says where it stands today.

  • Team Chat

    Direct messages and group rooms inside REDIS.4U, with attachments, unread counts, presence, mute, and a privacy screen-lock.

    Live

  • Asset Management

    Who has which phone, scanner, pallet jack or vehicle, and in what condition. Location is captured only when a documented action happens. Never continuous tracking of people.

    Planned

  • Fleet Management

    Registration, maintenance, service intervals and cost per mile, with the telematics already in your trucks on the same screen as orders and PODs.

    Planned

  • HR

    People records, hiring and onboarding, a document vault and e-signature, safety incidents, and driver qualification files.

    Planned

Get on the list

Want these bolted on?

IN-OUT and PAY-PRO are planned, not shipped. Leave your email and we'll tell you when they're ready for distributors on REDIS.4U.

If you'd like, tell us how you run time, payroll approvals or check deposits today. It shapes what we build first. No sales call, no spam.