Redwood Loader

Packages

Package	Company	Description	Sub-packages	Warehouse rows	Last load

Most recently loaded first. Click a package to see its sub-packages (feeds).

Feed	Load type	Target table	Status	Mapped columns	Warehouse rows	Last load

Click a sub-package to map its file columns and load a file. Edit changes how its files are read.

Status Rows to skip before header Leading columns to skip Min filled cells per row

Feed-specific date formats (optional; tried before the ) Expected header (optional, warns if different)

Partial load Rows with no measure Dimension 1 matching

Excel workbooks Sheets to load (comma-separated names; blank = the setting on the left) Sheets to ignore (only when "Sheets to load" is blank)

Carrier aliases (shipment) Location aliases (shipment)

Load confirmation e-mails Send to (comma-separated addresses)

Every load of this feed — upload, watcher / S3, e-mail or API intake, success or failure — mails the "Data Load Confirmation" to these addresses when sending is on. Blank = no e-mail even when on.

Default load type (recommendation) Default portal menu id (recommendation)

Rules — file-name rules and switches (legacy SUB_PACKAGE_RULES): PARTIAL_FILES pattern(s) separated by #_# load matching files as partial; 315 marks the 315 status files; ORDER_RELINK (value on) re-links a Portal Shipment file's orders to its shipment; XML_ROW names the XML element that makes a row.

Type	Value

File (CSV or Excel)

The header is read exactly as the load will read it: same delimiter detection, same quoting rules. Dates are matched against the , after any feed-specific ones set in the feed's settings.

#	File column	Example	UTILITY column	Track

Row identity: package + load_type + dimension1…12. A row whose key values already exist in the warehouse is updated; otherwise it is inserted. Measures and dates are overwritten by the incoming file.

The column mapping is set up by Redwood. If a column of your file is not mapped the way you expect, contact Redwood.

Recent loads for this feed

Run	File	Started	Outcome	Loaded	Rejected	Notes

Field changes recorded for this feed

When	Record	Field	Was	Now	Status	Ver.	Run · file	Line

Legacy MySQL

Read-only view of the WildFly loader's configuration: PACKAGE, SUB_PACKAGE_DETAIL, META, USER, COMPANIES. Nothing here can be changed from this screen.

ID	Package	Company	Supabase company	Sub-packages	META	Last load	Created by	Created	Deleted

Click a package to open it.

ID	Username	Name	Email	Role	Company	Packages	Last load	Last login	Deleted

Click a user to open their details.

Migrate a legacy package to Supabase PACKAGE → load.package · SUB_PACKAGE_DETAIL → feeds · META · LOAD_HISTORY · UTILITY* → warehouse.utility

Legacy ids are kept, so a package, run or META row that already exists in Supabase is left alone and re-running is safe. Nothing is written until you press Migrate; Dry run does every read and every decision and writes nothing.

ID	Package	Company	Supabase company	Sub-packages	META	Last load	Deleted

Click a package to run the pre-flight checks.

Master data only (ref.*) shared by every package — needed before the first shipment load of a package created here rather than migrated

Legacy ids are kept; rows already present are left alone, so re-running only adds what is missing.

File watcher

Loads CSV, Excel and XML files dropped into <dir>/<subPackageId>/ — one folder per feed, named by its id. A file is picked up once it has stopped changing, moved to processing/ while it loads, then to success/ or error/ (with a .log beside it). Several feeds load in parallel; one file per feed at a time. Tick files and press Load selected now to load them immediately — outside the scan, the settle wait and the watcher's slots (even while paused); they still wait for a load of the same feed that is already running. Create input folder makes a feed's folder (and its S3 prefix) before the first file arrives. Set with LOADER_WATCH_DIR, LOADER_WATCH_INTERVAL, LOADER_WATCH_PARALLEL in run-local.ps1.

loading…

Feed folders what is waiting right now

loading…

Recent loads by the watcher

When	Feed	File	Result	Detail	Run

Live log what the loader is doing right now — every load (upload, watcher, e-mail), newest at the bottom; refreshes with the screen follow

Entities

A saved view over a company's subpackages, joined on the columns of their files and shown under the file column names. A live entity is a view that runs the join on every read; a staging entity is a table rebuilt on a schedule (and, if asked, after each load of a member) — the loader measures the query before it saves and forces staging when a live view would be slow. Each entity can expose chosen columns through an API key.

Entity	Company	Mode	Members	Columns	Rows	Last built	Next refresh	API	Status

E-mail intake

A rule watches one mailbox folder for e-mails whose subject contains a text (optionally from a given sender), saves their .xlsx / .csv attachments to a local directory and copies them to an S3 path, then moves the e-mail to the Processed folder (or Error). Every e-mail and file is recorded below. Turning a rule on runs it immediately; after that it polls on its own interval.

Rules

Rule	Mailbox · folder	Subject contains	From	Types	Deliver to	Every	Last run	OK	Failed

Mailboxes

Name	Server	Username	Status	Last check	Rules

History e-mails handled, newest first

When	Rule	From	Subject	Outcome	Files	Notes

Runs (each check of a rule)

Started	Rule	Trigger	Status	Matched	Processed	Failed	Files	Error

API intake

An endpoint calls an external REST API on a schedule, pages through the response (and, when set, calls once more per record for its detail), writes the records to one file per output (Excel by default, or CSV) and delivers each file to its destination: an S3 path or directory as typed, or a feed's watcher folder, where the watcher loads it through the feed's mapping. Every run, file and HTTP call is recorded below; a file that went to a feed shows the load it got.

Endpoints

Endpoint	Source	Call	Outputs → destination	Schedule	Last run	Next run	Records	OK	Failed

Sources

Name	Company	Base URL	Auth	Throttle	Status	Last check	Endpoints

Runs every refresh, newest first — calls made, records extracted, files written and the load each file got

Started	Endpoint	Trigger	Status	Calls	Pages	Records	Files	Window	Took	Error

File lookup every line of every loaded file, searchable

Finds every line of the selected package's loaded files that contains the text (any column, case-insensitive). Searches the copies kept in S3; newest load first.

Text Loaded from to

Change history what changed, when, from which file — and what it was before

Only columns ticked chg (changes) or hist (every value) on the feed's mapping are recorded. Each block is one load: download that file, or the earlier file that carried the previous value, to verify a change.

Record	Field	Was	Now	Kind	Previous value came from	Line

Load history every run, every feed, newest first

Run	Package	Feed	File	Started	Completed	Outcome	Loaded	Rejected	User	E-mail	Notes

Users portal accounts (public.profiles) — who can sign in here

Email	Name	Role	Company	Active	Packages created	Loads	Last load	Created

Accounts are managed in the web portal; this list is read-only.

Companies public.companies

Company	Slug	Active	Users	Packages	Warehouse rows	Created

Standard date formats

loading…

Connections

checking…

API reference

loading…

No access

Packages

Legacy MySQL

Migrate a legacy package to Supabase PACKAGE → load.package · SUB_PACKAGE_DETAIL → feeds · META · LOAD_HISTORY · UTILITY* → warehouse.utility

Master data only (ref.*) shared by every package — needed before the first shipment load of a package created here rather than migrated

Jobs this session

File watcher

Feed folders what is waiting right now

Recent loads by the watcher

Live log what the loader is doing right now — every load (upload, watcher, e-mail), newest at the bottom; refreshes with the screen follow

Entities

E-mail intake

Rules

Mailboxes

History e-mails handled, newest first

API intake

Endpoints

Sources

Runs every refresh, newest first — calls made, records extracted, files written and the load each file got

File lookup every line of every loaded file, searchable

Change history what changed, when, from which file — and what it was before

Load history every run, every feed, newest first

Users portal accounts (public.profiles) — who can sign in here

Companies public.companies

Standard date formats

Connections

API reference

No access

Sign in

Packages + New package

New package

Edit package

⟲

Legacy MySQL

Migrate a legacy package to Supabase PACKAGE → load.package · SUB_PACKAGE_DETAIL → feeds · META · LOAD_HISTORY · UTILITY* → warehouse.utility

Master data only (ref.*) shared by every package — needed before the first shipment load of a package created here rather than migrated

Jobs this session

File watcher

Feed folders what is waiting right now

Recent loads by the watcher

Live log what the loader is doing right now — every load (upload, watcher, e-mail), newest at the bottom; refreshes with the screen follow Clear

Entities + Entity

E-mail intake + Mailbox + Rule

Rules

Mailboxes

History e-mails handled, newest first

Mailbox

Rule

API intake + Source + Endpoint

Endpoints

Sources

Runs every refresh, newest first — calls made, records extracted, files written and the load each file got

Source

Endpoint

Outputs — one file each

Run with a window

Download

Feed for this output

File lookup every line of every loaded file, searchable

Change history what changed, when, from which file — and what it was before

Load history every run, every feed, newest first

Users portal accounts (public.profiles) — who can sign in here

Companies public.companies

Standard date formats

Connections Re-check

API reference

Packages

Live log what the loader is doing right now — every load (upload, watcher, e-mail), newest at the bottom; refreshes with the screen follow

Entities

E-mail intake

API intake

Connections