A CHECK constraint rejects a row when its expression is false. An unknown result passes, which is why CHECK(amount >= 0) doesn't replace NOT NULL. Put both requirements in the schema when the value must exist and be nonnegative.
A DEFAULT supplies a value when an INSERT omits a column. It doesn't replace an explicit NULL. A UNIQUE constraint prevents duplicate values, but PostgreSQL normally treats NULLs as distinct. NULLS NOT DISTINCT changes that behavior when a business key must include at most one missing value.
Constraints protect every writer, including scripts that bypass an application form. Name the rule in plain language before encoding it. Avoid a check that depends on another row, because a row CHECK can't reliably enforce a cross-row total. Use appropriate keys, transactions or a different design for those requirements.
Zero stock is valid, missing stock isn't, and negative stock must fail.