Originally written by John Hardwick, last updated Jan 30, 2026, on the Swan Retail knowledge base (FRS).
This program holds a list of reasons why products are being booked into stock without a purchase order.
A write-on occurs when an item of stock has been identified where there is no corresponding purchase order.
This program is used when loading stock at time of go-live and / or possibly when selling customers product or items have been accepted without a purchase order being created.
Menu Location: System Admin > Warehouse > Set Up Write-Off Reasons
-
Click the NEW button or New on the side panel to generate a new record.
-
Click the icon to amend an existing record.
-
Once in amend / insert more, click the to save changes or to abort the action.
-
Click the CLOSE button, or Back option on the side panel to leave the page (or select another option from the menu)
|
Item |
Description |
|
Reason |
Specify a reason for the write-on. Why is the stock item being added to the stock holding |
|
Nominal Code |
Optionally specify a nominal account / GL posting code where the current cost value of the stock being written on is to be recorded. If not set, SwanFRS uses the default write-on account held in the application parameter settings. |
|
Active |
Tick to enable operators to use this write-off reason when removing stock from the stock holding. Untick to stop this reason code from being used within the warehouse stock management system. |
|
Legacy Default |
Ticking instructs SwanFRS that this write-on reason is to a be selected when informing SwanFRS of unexpected goods. |
|
Container Processing Default |
Ticking instructs SwanFRS that this write-on reason is to a used when recording the receipt of unexpected goods. |
|
Stock Take |
Tick to indicate the stock write-on is a result of a stock take, This is currently only used with sending data to the CSF accounts system |
Files from the Confluence page
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article