Teams you make once, and orders admins can correct
Match Prediction gains a reusable team catalog, admins can correct a Store order's details with an audit entry, and bundle-mode widgets boot in parallel.
01 ·Teams you make once and use again
Match Prediction gains a Create custom team action inside the Team A and Team B dropdowns. A team needs a name and takes an optional logo, and it saves to the community's own team catalog rather than to the match being edited. Custom teams sit in their own group beside the preset ones, search covers both, and a team created for one match is there for the next one and for later tournament rounds. Names are unique within a community once case and spacing are normalised, and the two sides of a match cannot both pick the same team.
Each match stores the chosen team's name and logo as a snapshot, so a saved match renders without a live catalog lookup. The authenticated application API takes the same team identity alongside the name and logo it already accepted.
Tournaments are the obvious case. A broker running a bracket over several weeks names the same teams in every round, and a catalog turns that into a one-time setup the later rounds draw on.
02 ·Admins can correct the details on an order
Order Details has an Edit action for admins who hold the permission. The customer-entered values become editable: account number, name, phone number, email and address. The order's own facts stay locked, so the order number, purchase date, product, redemption method, amounts and status cannot move through this route. Saving writes one audit entry recording who made the change, whether it came from the admin screen or the API, when, and which fields moved.
If the order changed while the panel was open the save is refused and asks for a refresh, and a save with nothing changed writes no audit entry. The same operation is available over an authenticated API as a partial update, with the same editable fields, the same validation and the same audit entry.
Fulfilment goes wrong on a mistyped address. Letting the admin who takes the customer's call fix it closes the matter in the same hour, and the audit entry is what makes that safe to delegate.
03 ·Bundle-mode widgets boot in parallel
In the SDK's bundle mode, a widget now starts its own data and its community metadata at mount, alongside the sign-in round trip, and warms the view chunk its layout will actually render while authentication runs. Prefetched requests are consumed once and fall back to a fresh call when one fails, so a miss costs nothing. Measured cold against a staging fixture, the milestone widget reached visible content about a quarter sooner, with the warm case close behind. Streak, Mini Games and Store widgets took the same treatment.
Widget boot time is the part of a broker's page they cannot profile, because it happens inside our bundle. Every second removed there is a second sooner that a trader sees their streak or their store.
Store, socials and referral widgets in iframe mode start loading their code the moment the widget initialises, as does the referral SDK widget.
19 Aug