Retail Express writeback
Retail Express writeback
Settings → Integrations → Retail Express → Writeback configures native
price and lifecycle updates. An owner or admin first
tests and saves the Rex connection,
then enables the actions the workspace should send.
The managed import stays read-only. Native writeback uses its own encrypted
credentials and changes Rex only for the approved actions described below.
Approved price changes
- An admin chooses Sell price (tax inclusive) or Web price (tax
inclusive), enables Price changes, and saves the settings. - A buyer approves a new price decision in Twelfth for a product with a valid
Rex product ID. - Twelfth reads the Rex product, updates the selected price field, and reads
the product again to confirm the approved price. - Review the decision’s Delivered to block for the destination, result,
Rex product reference and any error. A confirmed native price is recorded
as Executed on the decision ledger.
An approval updates the selected field only; choosing sell price does not also
change web price. Other product fields are preserved. Earlier decisions are
not automatically sent when a connection is first configured. Changing keys,
instance or the target price field establishes a new approval boundary: review
and approve a new price for a decision that predates it.
Verify a controlled write
Test connection authenticates and reads products; it does not change a product
or prove write permission. Use a designated test product and preserve its
current price. Create a new price approval after connecting, effective today,
then check Executed and the actual price in Rex. Restore the original price
directly in Rex after the test.
For an EOL test, preserve the original lifecycle value, confirm the mapped
update, and inspect that field in Rex. Restore the original value in Rex after
the test; unmuting does not reverse an external lifecycle change.
When a price needs review
- Future-dated price: native writeback does not schedule it. Retry on its
effective date after reviewing the decision. - Missing or invalid Rex product ID: check the source product mapping.
- Sell price changed since approval: review the current Rex price and
approve a new decision. Twelfth will not apply the stale sell-price snapshot. - A newer price was already delivered: an older approval will not overwrite
that newer delivery. - Unknown write outcome: inspect the product in Rex before creating another
price decision. A lost reply does not cause an automatic repeat write; a
later check may confirm the intended price is already there.
Turning Price changes off pauses delivery and keeps the saved connection.
It does not reverse prices already applied. The next managed import brings
source data back on its normal schedule; successful writeback is not an
immediate refresh of every workspace view.
End-of-life decisions
An admin maps an existing Rex attribute and value under
End-of-life decisions.
Lifecycle updates use the saved pricing credentials, with their own switch.
When muting a product from a routine or one of its task lines:
- Choose Reason → End of life (EOL).
- Review Also update the connected system. If selected, Twelfth shows the
connector, field label and value that confirmation will send. - Keep it selected to queue that product update, or clear it to record EOL
locally. If no lifecycle mapping is enabled, EOL is recorded locally. - Confirm the mute, then check its result on the routine or in Writeback →
Recent lifecycle decisions.
Twelfth assigns the mapped value to that Rex product while preserving its
other attributes. It does not rename an attribute or value for the whole Rex
catalogue. If Rex already has the selected value, Twelfth confirms it without
sending another change.
Unmuting or ending the mute resumes the routine’s local eligibility; it does
not reverse the lifecycle value already applied in Rex. Review that value in
Rex separately if it needs changing.
A lifecycle choice creates one product-update decision in Decisions. Native
confirmation records Executed on that same decision item. A local-only
choice remains recorded and is excluded from external delivery, including
later manual and nightly reconciliation. Structured EOL reasons on committed
review lines use the same recorder and configured mapping. Other systems can
receive explicitly opted-in product-update exports through Destinations.
Read the result
| Result | What to do |
|---|---|
| Recorded locally / No lifecycle mapping | The decision is recorded without a new external update. Enabling a mapping later does not backfill it. |
| Update queued / Updating connected system | Wait for processing; the history refreshes while an update is pending. |
| Update confirmed | Rex returned the selected attribute value. |
| Update failed | Read the error, fix the cause, then use Retry update where offered. The deciding buyer or an admin can retry failed actions. |
| Outcome unknown · review in source system | Check the Rex product before making a new lifecycle decision; Twelfth does not blindly repeat the write. |
| Update cancelled | The connection or mapping changed, the mute ended before processing, or a newer decision superseded it. Review before making a new decision. |
Purchase orders and stock transfers
Purchase orders and Stock transfers are Unavailable in native Rex
writeback. Saving subscription keys does not enable these actions.
To prepare Rex mass-upload files, use Settings → Integrations → Destinations →
Add a destination → Google Sheet. Twelfth can write a Google Sheet or an
Excel workbook kept in Google Drive.
For an existing Rex upload tab, select Keep this tab’s columns exactly as they
are. Twelfth fills only its own mapped columns without adding tracking
columns; instructions, supplier and outlet cells, and other template content
stay in place. Preview the mapping and check the supplier and outlet before
your team uploads the file into Rex. Writing the workbook prepares the upload;
it does not raise an order or transfer in Rex.
Twelfth can also set up an order workbook with a tab per supplier, using the
supplier’s Rex code from the inbound warehouse sync. Missing supplier codes
hold those lines back. Order and transfer lines with zero quantity are not
delivered. Cleared rows in a template whose columns are kept exactly are not
refilled, and that mode has no spreadsheet read-back.
See Spreadsheet destinations
for sharing, mapping, previews and delivery settings. A custom API destination
can send to an order bridge your team provides; its Rex preset is separate
from native writeback and requires your endpoint and credential.