Apps Script example · 11 min read

Assign Marketplace Seller Performance Tiers: Copy-Paste Apps Script Pattern

Working assign marketplace seller performance tiers example in Apps Script—copy-paste code, common mistakes, and when to get it built professionally.

SpreadsheetAppTime-drivenSellers

Map late shipment, cancel rate, and rating into Platinum–Bronze seller tiers. The workbook becomes the system of record; Apps Script owns the joins and business rules so analysts are not pasting monthly formulas.

Entry point `assignSellerTiers` reads typed columns with SpreadsheetApp batch APIs. SpreadsheetApp is the primary service; Time-driven describes how you usually invoke it after authorization.

Keep thresholds (grace days, bands, alert emails, API keys) in Config cells or Script Properties so the same .gs file promotes from sandbox to production without code edits.

This page is technical only: sheet layout, edge cases, runnable code, deploy steps, and FAQs for assign marketplace seller performance tiers. No consulting pitch—just the pattern you can paste and harden.

Need this built? Hire a Google Apps Script developer →

Sheet / project setup

TabColumnsNotes
SellersSeller, LateRate, CancelRate, RatingWindow
TiersLabelOutput

What this script does

assignSellerTiers() map late shipment, cancel rate, and rating into Platinum–Bronze seller tiers.

  • Late/cancel/rating
  • Four tiers
  • Window metrics

Prerequisites

Container-bound script on the workbook that contains the tabs in the setup table. Authorize SpreadsheetApp scopes on first run.

  • V8 runtime
  • Exact sheet names
  • Script timezone = ops timezone

Walkthrough

Threshold ladder on late/cancel/rating → PLATINUM/GOLD/SILVER/BRONZE.

Paste the code, set Config/Properties, run assignSellerTiers once, verify the output tab, then attach a Time-driven trigger.

Edge cases

Metrics should be trailing-window rates, not lifetime, or tiers will lag reality.

Testing

Use a sandbox copy with 3–5 known rows. Compute expected outputs for assign marketplace seller performance tiers offline, run assignSellerTiers, and diff the output tab including one intentional bad row.

Hardening

Add LockService around multi-sheet writes if triggers can overlap. Log run timestamps. Keep API keys and alert emails in PropertiesService—not in shared cells.

Variations

Fork ideas: filter to one business unit, change grain (daily→weekly), or POST a summary payload after assignSellerTiers succeeds.

Operations notes

Assign an owner for the output tab, document regenerate steps, and treat `assignSellerTiers` as source of truth over ad-hoc cell formulas.

Full code: assignSellerTiers()

Run assignSellerTiers when source tabs are current. Edit sheet names and Config/Properties first.

function assignSellerTiers(){
  const ss=SpreadsheetApp.getActive();
  const rows=ss.getSheetByName('Sellers').getDataRange().getValues().slice(1);
  const out=rows.map(r=>{
    const late=Number(r[1])||0, cancel=Number(r[2])||0, rating=Number(r[3])||0;
    let tier='BRONZE';
    if(late<=0.02 && cancel<=0.01 && rating>=4.7) tier='PLATINUM';
    else if(late<=0.05 && cancel<=0.02 && rating>=4.5) tier='GOLD';
    else if(late<=0.08 && cancel<=0.03 && rating>=4.2) tier='SILVER';
    return [r[0],late,cancel,rating,tier];
  });
  const sh=ss.getSheetByName('Tiers');
  sh.clearContents();
  sh.appendRow(['Seller','LateRate','CancelRate','Rating','Tier']);
  if(out.length) sh.getRange(2,1,out.length+1,5).setValues(out);
}
  1. Line 1: Entry point — bind triggers to assignSellerTiers.
  2. Line 3: Batch read; avoid per-cell getValue in loops.
  3. Line 15: Batch write output rows in one setValues call.
  4. Line 5: Rename sheet constants before production.
  5. Line 6: Rename sheet constants before production.

Deploy this example

  1. 01

    Open Apps Script

    In the bound spreadsheet: Extensions → Apps Script. For standalone projects, create one at script.google.com and link your Sheet by ID.

  2. 02

    Paste and save

    Add a .gs file, paste the code below, rename constants at the top (sheet names, column letters, API property keys), then save.

  3. 03

    Authorize once

    Run the main function from the editor. Accept OAuth scopes when prompted — triggers cannot run until authorization succeeds once.

  4. 04

    Add the trigger

    Triggers → Add trigger → choose the handler function and event (time-driven, on edit, or on form submit). Delete test triggers before production.

Before you run: assign marketplace seller performance tiers

  • 1Setup tabs exist with headers matching assignSellerTiers
  • 2Dry-run on a copy workbook
  • 3Timezone verified
  • 4SpreadsheetApp authorization completed
  • 5Output spot-checked against hand calc
  • 6Time-driven trigger added only after validation
  • 7Owners + alert recipients documented

Frequently asked questions

At minimum the tabs listed in the setup table for Assign Marketplace Seller Performance Tiers. Output tabs may be cleared each run—do not store source-of-truth data there.

Run from the Apps Script editor for dry runs. Production usually uses a Time-driven trigger after OAuth succeeds once.

Metrics should be trailing-window rates, not lifetime, or tiers will lag reality.

Per-cell calls burn quota and wall time. One read + one write keeps this pattern under the 6-minute execution cap longer.

PropertiesService (Script Properties) for API keys and alert inboxes. Config sheet is fine for non-secret thresholds.

Simple ratios maybe; assign marketplace seller performance tiers needs joins, branching, or side effects (email/Docs/API) that Apps Script handles cleanly.

Keep the .gs in clasp/git. Avoid divergent copies of formulas on the output tab—regenerate from the script.

Related examples

Want this wired into your real workflow?

I adapt these patterns to your Sheet structure, APIs, and triggers — deployed in your Google account. Fixed-scope quotes from $500 · free 30-min consult · quote within 24 hours.