"Physical" properties — margin-left, left, padding-right — always point at an actual screen direction. Switch a page to a right-to-left language like Arabic or Hebrew, and margin-left: 14px still creates 14px on the visual left — but in RTL, "start" is the right, so that margin now sits on the opposite side from where the text flow begins.
Logical properties are named after text flow instead of screen coordinates. margin-inline-start means "the margin on the side where text begins" — the left in LTR, the right in RTL, automatically. inset-inline-start (a left/right that flips with RTL) and padding-block (top/bottom's counterpart) follow the same idea: inline is the axis text flows along, block is the axis lines stack along.
Under vertical writing modes (writing-mode: vertical-rl, used in traditional Japanese and Chinese typesetting), inline and block swap which screen axis they even point at. Written with logical properties, a layout follows every one of those changes — language, direction, writing mode — without a single value being touched, which makes them close to mandatory for any multilingual product.
When to use
If a product might ever support an RTL language like Arabic or Hebrew, it's worth defaulting to logical properties from the start rather than retrofitting margin-left/right, left/right and padding-left/right later. If every supported language is LTR with no plans otherwise, it's not urgent.